aboutsummaryrefslogtreecommitdiff
path: root/git-codereview/gofmt.go
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2015-01-30 10:45:20 -0500
committerRuss Cox <rsc@golang.org>2015-01-30 18:19:19 +0000
commitc283ee0bf4c9a58240df02dc6bc62152ee935fb4 (patch)
tree890de77c2ee052df134514b9a773eeb8e80dfa1d /git-codereview/gofmt.go
parent18314f7ef99b73828d56cef081ee5a9572fe902c (diff)
downloadgo-x-review-c283ee0bf4c9a58240df02dc6bc62152ee935fb4.tar.xz
git-codereview: revise pending
- Use multiple commit output form always. We're going to start suggesting the use of multiple commits, and it is confusing to flip between the two displays based on the number of commits. - Document pending -c option (current branch only). - Add pending -s option (short form). While doing this, I got my client into a state where I had a tag and a branch with the same name. Make things work in that mode too. Change-Id: I4a3d73ce88be78b04d5bc4e56f1e3bed435cfde7 Reviewed-on: https://go-review.googlesource.com/3621 Reviewed-by: Andrew Gerrand <adg@golang.org> Reviewed-by: Rob Pike <r@golang.org>
Diffstat (limited to 'git-codereview/gofmt.go')
-rw-r--r--git-codereview/gofmt.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/git-codereview/gofmt.go b/git-codereview/gofmt.go
index 96b5e86..4608a3a 100644
--- a/git-codereview/gofmt.go
+++ b/git-codereview/gofmt.go
@@ -120,7 +120,7 @@ func runGofmt(flags int) (files []string, stderrText string) {
// Find files modified in the index compared to the branchpoint.
branchpt := b.Branchpoint()
- if strings.Contains(cmdOutput("git", "branch", "-r", "--contains", b.Name), "origin/") {
+ if strings.Contains(cmdOutput("git", "branch", "-r", "--contains", b.FullName()), "origin/") {
// This is a branch tag move, not an actual change.
// Use HEAD as branch point, so nothing will appear changed.
// We don't want to think about gofmt on already published