-
Notifications
You must be signed in to change notification settings - Fork 49
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
Branch renaming and protection #80
Labels
Comments
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story. The labels on this github issue will be updated when the story is started. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm opening and then very shortly closing this issue to document a couple of things that I've just done.
One, I've enabled branch protection, requiring PRs and at least two reviewers.
Two, I've renamed the
master
branchrelease
to align with the broader git ecosystem's deprecation ofmaster
as default branch name.I've done this to gain experience with these settings and changes, as broader VMware policy expects both things, and this is a relatively low-risk repo on which to start rolling these changes out across the TAS-ecosystem repos in the
pivotal
org.One or both of these may cause automation breakage, or provoke the need for followup actions; if you need help, make an issue and tag me, I'll sort it out.
The text was updated successfully, but these errors were encountered: