Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
all: either enforce prefix for non-master branches with automation, or remove the requirement #34793
The process for making changes to branches other than
We should find out why the convention exists and document the rationale for it (so that when time passes and people forget why we're doing it, it's possible to look it up and confirm the reason is still applicable).
If it turns out the reason for doing so is still valid, we should improve tooling to catch cherry-pick CLs that have the wrong prefix.
If it turns out there is no reason to add the prefix anymore, we should change the cherry-pick process to remove that requirement.
Possibly related issue #13202.