| Issue 1803: | Manually pushing a change to a *different* branch marks the patch as merged | |
| 5 people starred this issue and may be notified of changes. | Back to list |
************************************************************ ***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW ***** ***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL ***** ***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC. ***** ***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS! ***** ************************************************************ Affected Version: 2.5.2 What steps will reproduce the problem? 1. Create a patch set destined for branch foo 2. Have someone with privileges manually push that change to branch bar (say to deploy to a testing system) 3. Notice that the page for the change is now marked as merged, with a comment that it was merged into branch bar. It is now impossible to merge it with branch foo as it was intended (through the web interface, can still manually do it) What is the expected output? What do you see instead? I would expect that I can still merge the change into the original branch it was destined for Please provide any additional information below.
Oct 10, 2013
are there any updates to this defect? This is pretty annoying.
Jan 16, 2014
Hello, Just wanted to know if this issue is already resolved or someone has already updated a change for this issue? |
|
| ► Sign in to add a comment |
This could cause issues in the following situation. - user pushes a change to review - user then pushes (directly) to a branch patter such as ref/heads/${username}/* - the original change would now be marked as merged