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

standarize branch protection rules #13

Open
amanmdesai opened this issue Aug 30, 2022 · 7 comments
Open

standarize branch protection rules #13

amanmdesai opened this issue Aug 30, 2022 · 7 comments
Assignees

Comments

@amanmdesai
Copy link
Contributor

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

@klieret
Copy link
Member

klieret commented Sep 2, 2022

Needs to be done on a per-repo basis. I've done this for a few...

@amanmdesai
Copy link
Contributor Author

thank you

@klieret klieret self-assigned this Sep 2, 2022
@wdconinc
Copy link

Can we list here what the branch protection rules should be?

Suggestion:

  • Require a pull request before merging
    • Require approvals:
      • Number of required approvals: 1
    • Dismiss stale pull request approvals when new commits are pushed
  • Require status checks to pass before merging
  • Require conversation resolution before merging

Also, general options, only allow:

  • Allow squash merging
    • Default to pull request title and description

@klieret
Copy link
Member

klieret commented Oct 31, 2022

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.

@wdconinc
Copy link

I guess we won't run into long PR commit histories that are unbuildable, so I don't think squash merging is critical.

@stale
Copy link

stale bot commented Dec 30, 2022

This issue or pull request has been automatically marked as stale because it has not had recent activity. Please manually close it, if it is no longer relevant, or ask for help or support to help getting it unstuck. Let me bring this to the attention of @klieret @wdconinc @michmx for now.

@stale stale bot added the stale label Dec 30, 2022
@wdconinc
Copy link

wdconinc commented Dec 4, 2023

https://github.com/organizations/hsf-training/settings/rules/ allows organization rulesets but only for enterprise. Created ruleset, but left it disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants