You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: