-
Notifications
You must be signed in to change notification settings - Fork 1
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
standarize branch protection rules #13
Comments
Needs to be done on a per-repo basis. I've done this for a few... |
thank you |
Can we list here what the branch protection rules should be? Suggestion:
Also, general options, only allow:
|
I'm against the "only squash merging" and the "dismiss stale PR approvals" TBH. I personally generally wouldn't make things to restrictive. Requiring PRs as the normal workflow would be great though. And conversation resolution is easy enough. |
I guess we won't run into long PR commit histories that are unbuildable, so I don't think squash merging is critical. |
https://github.com/organizations/hsf-training/settings/rules/ allows organization rulesets but only for enterprise. Created ruleset, but left it disabled. |
repositories have different branch protection rules, some are protected whereas some are not protected.
Instructions
Thanks for contributing! ❤️
If this issue is about a specific episode within a lesson, please provide its link or filename.
Keep in mind that lesson maintainers are volunteers and it may take them some time to respond to your contribution.
To ensure that the right people get notified, you can tag some of the last contributors with
@githubname
.Although not all contributions can be incorporated into the lesson materials, we appreciate your time and effort to improve the curriculum. If you have any questions about the lesson maintenance process or would like to volunteer your time as a contribution reviewer, please contact the HSF training convenors (contacts here).
You may delete these instructions from your issue.
- HSF Training
The text was updated successfully, but these errors were encountered: