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

Branch protection and merge rules? #119

Open
story645 opened this issue Nov 7, 2022 · 4 comments
Open

Branch protection and merge rules? #119

story645 opened this issue Nov 7, 2022 · 4 comments

Comments

@story645
Copy link
Member

story645 commented Nov 7, 2022

Hey folks, do we want to enable branch protection? and do we want a certain # of reviews to merge stuff? attn: @rougier

@jklymak
Copy link
Member

jklymak commented Nov 7, 2022

I think our policy has been @rougier merges. It he can relinquish that if he likes, in which case I think one review is ok unless a re-architecture.

@rougier
Copy link
Member

rougier commented Nov 28, 2022

I'm not familiar with branch protection so I cannot really answer. Note that I'm late on GitHub notifications so do not wait for my review if too late (or you can mail me if really urgent)

@story645
Copy link
Member Author

Branch protection means that GitHub will disallow pushing directly to main (well technically whichever branch you want) & won't let folks edit directly on main. https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches

@rougier
Copy link
Member

rougier commented Nov 28, 2022

Thanks for the explanation. Not strong opinion on that, I'll follow your advice and expertise.

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

3 participants