-
Notifications
You must be signed in to change notification settings - Fork 43
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
Protected branch for main? #119
Comments
+1 for auto-merging, especially for bot-generated maintenance PRs. I think we're probably ready to implement the "require a review from a codeowner" rule now that we have a sensible team-based codeowner system in place, so that it's very unlikely we'll be stuck waiting on any one individual who might be away/unavailable to review. |
EWG today on board with protecting |
Do we want to make main a protected branch? This means that force-pushing to and deleting the branch is disallowed for everyone (unless we specifically allow it). We also have these options available to us:
The last one is one I'm interested in, not as a gate-keeping exercise, but it allows us to use "auto-merge". With that we can mark a PR to merge as soon as all of the required checks pass.
The text was updated successfully, but these errors were encountered: