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

all: either enforce prefix for non-master branches with automation, or remove the requirement #34793

dmitshur opened this issue Oct 9, 2019 · 3 comments


Copy link

@dmitshur dmitshur commented Oct 9, 2019

The process for making changes to branches other than master is described at It requires adding a "[branch-name]" prefix to the commit message. However, it doesn't describe the motivation for doing so. I've asked around and so far no one knows.

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.

/cc @golang/osp-team

Possibly related issue #13202.

@dmitshur dmitshur changed the title all: either enforce prefix for non-master branches with a bot, or remove the requirement all: either enforce prefix for non-master branches with automation, or remove the requirement Oct 9, 2019
@dmitshur dmitshur added this to the Unreleased milestone Oct 9, 2019
Copy link

@FiloSottile FiloSottile commented Oct 9, 2019

I am mildly in favor of keeping the prefix. It makes CLs easily distinguishable from their cherry-picks, for example. We should definitely have a bot check.

Copy link

@bradfitz bradfitz commented Oct 9, 2019

Russ is in favor of keeping them too. (Just discussed in unrelated meeting)

Once we have #18548 this is another easy check to add to that.

Copy link

@katiehockman katiehockman commented Oct 9, 2019

Can we have Gerrit auto-fill that prefix when we use the UI to create the cherry pick?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.