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

Use branch protection rules #11

Open
Peter9192 opened this issue Apr 11, 2022 · 0 comments
Open

Use branch protection rules #11

Peter9192 opened this issue Apr 11, 2022 · 0 comments

Comments

@Peter9192
Copy link
Contributor

Make it impossible to push directly to master/main and require at least one approving reviewer before PRs can be merged.

This helps to

  • Ensure code quality
  • Make sure others notice the changes that are made
  • Document changes to the code (with descriptive top posts, PR conversation, and by linking PRs to issues)

https://docs.github.com/en/enterprise-server@3.4/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-pull-request-reviews-before-merging

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

No branches or pull requests

1 participant