| Issue 2881: | Related Changes should appear also for merged changes | |
| 4 people starred this issue and may be notified of changes. | Back to list |
Affected Version: 2.9 If the user has a chain of commits which he needs to submit one after the other (cherry-pick strategy), then the Related Changes tab is very useful to iterate over the changes one by one and submit. The problem is that it disappears right after submitting the change. For merged changes, it is useful to have at least the parent and direct child commits (maybe also cherry picks).
Sep 3, 2014
#1
org...@gmail.com
Sep 3, 2014
It's not related to the merge strategy. The related changes tab is not shown at all for merged changes. IIRC this was by design. I also seem to remember seeing and issue reported about this before.
Sep 3, 2014
There is issue 2308 which you fixed :)
Sep 3, 2014
Sorry, you approved.
Sep 3, 2014
Right, that's the one I was thinking of. Seems like this case is different though; looks like the cherry-pick strategy is relevant here, as you wrote.
Sep 8, 2014
Issue 2887 has been merged into this issue.
Sep 18, 2014
https://gerrit-review.googlesource.com/60200 It currently shows only child commits, but that's a start. |
|
| ► Sign in to add a comment |