We just started using this plugin Git Integration for Jira.
And hence quite a few files were committed without the commit message format of having the JIRA ticket number in commit message.
Can some one please provide some pointers?
Thanks a lot,
Hello Rumpa -
Just following up on our conversation we had via email about evaluating the Git Integration for JIra Cloud add-on.
In the Jira Cloud product we offer the ability to modify the association of the commit with a Jira issue. You can see a video on how to do this here: https://bigbrassband.wistia.com/medias/kmvlr97c3x
On our Jira Server product - we don't (yet) have this feature - but we do index git notes which allows you to add a note to a commit after the fact which could include a new Jira issue key.
Let me know if you have any additional questions.
In order to change old git commits you would have to use rebase to get back to the commit you want to change:
git rebase --interactive '<sha-1 commit number>^'
That will start the interactive rebase and it will allow you to edit your commit comment. Once you are done editing, commit your changes:
git commit --all --amend --no-edit
Then continue your rebase:
git rebase --continue
To get back to the HEAD.
Just be careful when you push, the rebase will change the SHA-1 of that commit and it's children, so it rewrites the history in the repository from that point on. Do not use git push --force, that can break your repository.
Gaining insight into your team’s effectiveness and choosing the right estimation technique. Estimating projects is hard. It is because people have the tendency to underestimate the time thin...
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