-
Notifications
You must be signed in to change notification settings - Fork 896
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
Comments
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. |
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) |
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 |
Thanks for the explanation. Not strong opinion on that, I'll follow your advice and expertise. |
Hey folks, do we want to enable branch protection? and do we want a certain # of reviews to merge stuff? attn: @rougier
The text was updated successfully, but these errors were encountered: