Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

restricting pull requests #47

Open
dicook opened this issue Oct 26, 2021 · 1 comment
Open

restricting pull requests #47

dicook opened this issue Oct 26, 2021 · 1 comment

Comments

@dicook
Copy link
Contributor

dicook commented Oct 26, 2021

can we put a restriction so that pulling from published to master is prevented? we need to pull from master into published, but this has to be orchestrated from the published branch, and it is easy to make the pull the wrong way.

@s-u
Copy link
Member

s-u commented Jan 5, 2024

I'm not sure that GH has fine enough control for this. Ideally, PRs should be into master and once it is considered good the commits should be simply added to published. The default is now to make master and the target in PRs so that should be good.

I have disabled merge commit PRs which should at least help with master and published diverging (we had them diverge significantly albeit they had the same content which made it hard to track changes). Part of the problem is that we have two kinds of PRs: "real"ones, i.e. contributed changes to master, and then the final merge from master to published which is just a technicality --- as long as they don't diverge it's just

git checkout published && git pull origin master && git push origin published

so maybe easier than using PRs for it.

In theory one can add a change to published and then rebase master (since the effect is identical), but I agree that it should be avoided on conceptual grounds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants