| Issue 1512: | "Can Merge" says "No" when it should say "Yes" | |
| 3 people starred this issue and may be notified of changes. | Back to list |
I don't know how to reproduce, but patchset 1 of: https://gerrit-review.googlesource.com/#/c/37280/ Is capable of merging yet "Can Merge" says "No".
Aug 21, 2012
#1
dashkov...@gmail.com
Aug 22, 2012
The configuration of git-repo [1] is set to "Fast Forward Only", so I think this is the expected behaviour. If a change is not based on the latest head, it can't be submitted until it is rebased. [1] https://gerrit-review.googlesource.com/#/admin/projects/git-repo
Aug 23, 2012
(No comment was entered for this change.)
Status:
Invalid
Aug 23, 2012
It was rebased. and when I push REBASE button, it says "up to date" on black screen.
Aug 23, 2012
(No comment was entered for this change.)
Status:
New
Aug 24, 2012
I also saw this issue one or two times. "Can Merge" wrongly stated "No", it only recovered after another change was merged, which I guess cause the "Can Merge" flag to be recomputed. Unfortunately I also can't say how to reproduce this. |
|
| ► Sign in to add a comment |