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
Currently git-codereview doesn't add the appropriate "[branch]" prefix to commit messages created or amended during a rebase because all it sees is the detached HEAD state. As a fall back, it could look for .git/rebase-merge/head-name, which contains the full ref name of the branch being rebased and find that branch's upstream.
…tion
`Branch.OriginBranch()` does not return the upstream branch name when
a commit is made during a rebase. Add handling to get the upstream
branch name of the rebase branch when `Branch.OriginBranch()` fails to
return a branch name.
Fixesgolang/go#21164
Change-Id: I59ea724d9660dce72b22bf6f3b7ee2606cf6f8ae
r5d
added a commit
to r5d/review
that referenced
this issue
Jan 3, 2022
`Branch.OriginBranch()` does not return the upstream branch name when
a commit is made during a rebase. Add handling to get the upstream
branch name of the rebase branch when `Branch.OriginBranch()` fails to
return a branch name.
Fixesgolang/go#21164
Change-Id: I59ea724d9660dce72b22bf6f3b7ee2606cf6f8ae
Currently git-codereview doesn't add the appropriate "[branch]" prefix to commit messages created or amended during a rebase because all it sees is the detached HEAD state. As a fall back, it could look for .git/rebase-merge/head-name, which contains the full ref name of the branch being rebased and find that branch's upstream.
For example, this happened in https://golang.org/cl/50875.
/cc @josharian
The text was updated successfully, but these errors were encountered: