| Issue 1489: | rebase button set commiter to Gerrit | |
| 10 people starred this issue and may be notified of changes. | Back to list |
Affected Version: 2.4.2 What steps will reproduce the problem? 1. Create a change which has for parent an old commit and send it to git 2. Look at the patchset in the GUI, committer field should be yourself 3. Press Rebase button 4. Look at the new patchset in the GUI, committer is set to gerrit2@example.com What is the expected output? What do you see instead? I would expect the automatically rebased patchset to use as committer name whoever did press the rebase button.
Jul 24, 2012
#1
amu...@wikimedia.org
Jul 25, 2012
A similar issue happen with the revert button. The committer is set to gerrit user email too.
May 30, 2013
i don't understand this design decision, this design include a problematic flow when a commit is merged and runs a job in jenkins. since the committer is 'gerrit2' then if a build fails in jenkins, the original commiter won't receive an email alerting him that his patch failed the build.
Aug 12, 2013
We had the same problem here. jenkins e-mail is sent to gerrit e-mail address instead of the user of the original patch set. I hope this will be changed soon. Because of this we will advise our developers not to use these two functions. Is there an easy way to deactivate the buttons?
Aug 12, 2013
It would be really helpful if this could be changed, or if it is debatable, adding a property in some configuration file to switch between gerrit email address in rebase commit and original committer's email address would be sufficient.
Nov 4, 2013
I think this should be fixed with this change: https://gerrit-review.googlesource.com/#/c/45733/ which has been merged within Gerrit 2.8
Nov 4, 2013
(No comment was entered for this change.)
Status:
Submitted
Labels: FixedIn-2.8
Dec 9, 2013
(No comment was entered for this change.)
Status:
Released
|
|
| ► Sign in to add a comment |