|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I thought that if the commit which was created prior to "git commit --amend" were seen by the Jenkins job, then after the "git commit --amend" that prior commit would now be "detached" because there are no longer any references to the prior commit.
I'm not a gerrit user, so I may misunderstand the use cases, but I'm accustomed to "git commit --amend" leaving an "orphan" commit in the git reflog.