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

Enable master branch protection, require Pull Requests for changes to this repo #84

Open
dhunteratg opened this issue Jul 26, 2023 · 0 comments

Comments

@dhunteratg
Copy link

A good form of GitHub etiquette would be to enable Branch Protection on the master branch so that no on can commit directly to the master branch. This would force all users of this repository (Arista employees included) to create branches to track a group of changes and then perform a Pull Request to land those changes in the master branch.

https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches

The motivation behind this request is that commits made directly to the master branch do not trigger Github to send any notifications for changes, while merging Pull Requests does send notifications. As a customer that tracks the changes to several studios, this would help me stay on top of changes to this repository.

Thanks!

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