| Issue 2331: | change-merged event contains wrong patch set number when using cherry-pick merge strategy | |
| 4 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.8 As reported by David Tweet on the repo-discuss list [1] [1] https://groups.google.com/forum/#!topic/repo-discuss/am-au1QCnMA What steps will reproduce the problem? 1. Push a commit for review which creates a new change with patchset 1, abc123 2. Push another patchset on the same review, patchset 2, bcd456 3. Submit the change, which automatically creates patchset 3, cde789 4. Observe gerrit stream-events for the change-merged event. Actual result (bug): The event json contains: "patchSet": { .. "number": "2", "ref": "refs/changes/89/8989/2", "revision": "bcd456", ... } Expected Result: The event json contains: "patchSet": { .. "number": "3", "ref": "refs/changes/89/8989/3", "revision": "cde789", ... }
Feb 11, 2014
Project Member
#1
bassem.rabil
Feb 11, 2014
https://gerrit-review.googlesource.com/#/c/54570/
Status:
ChangeUnderReview
Labels: Blocking-2.8.2
Feb 14, 2014
(No comment was entered for this change.)
Status:
Submitted
Labels: -Blocking-2.8.2 FixedIn-2.8.2
Mar 11, 2014
(No comment was entered for this change.)
Status:
Released
|
|
| ► Sign in to add a comment |