It is not infrequent that after a commit is made in git and subsequently pushed upstream (we use Atlassian Stash), the commit message is realized to contain the incorrect Jira issue Id.
Any documentation I have seen regarding modification of git messages after pushing to a shared repository says simply don't do it. Yet it is common to find commits related to the wrong Jira ticket. With svn, it was fairly trivial to update the relevant commit message - we just notified eveyone to update cached logs. It seems not so easy with git.
So, I am curious whether anyone has found a way to resolve these seemingly conflicting needs: git's need to not change history and Jira's need to change git history to associate commits with the correct issue.
One approach would be to remove Jira's dependency on the commit message and maintain the associations between Jira ID and commits outside of git. I have not found any existing solution with this approach but I do have a feature request for it at Atlassian [JRA-33338]. Please vote for it while there.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs