-
Notifications
You must be signed in to change notification settings - Fork 11
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 #39
Comments
Done. Additional options regarding approvals appeared when I checked "Require a PR before merging". I didn't check any of these as I don't want to require approvals at this stage. Let me know if you think we should make any other changes to this too! |
Update: I think "lock branch" really makes the branch read-only (won't allow merging PRs). I unchecked this. I am not sure if this is the behaviour but I went to merge #34 with "lock branch" checked and it wouldn't allow me. Unchecked now and it does. |
I suggest we enable "branch protection" for main -- basically this stops people (and people definately includes me) from accidentally pushing to main. I've done this in other projects accidentally.
This actually comes with a whole bunch of settings, here is the list, and my experience of them with another fairly large multi-person project ( GAP at gap-system/gap ), but I'm very happy for people to disagree, and also we could try changing settings later.
The text was updated successfully, but these errors were encountered: