Enforce the JIRA issue id in a GIT commit message
This can be done by using git hooks file location at .git/hooks/commit-msg. Following are the 2 way in whcih each Developers can set the Hooks in their developement envioronment.
Method – 1
# This hook will make sure that the commit message contains a JIRA issue.
# To enable this hook, rename this file to ".git/hooks/commit-msg".
# Make sure to add execution permissions to the file.
if [[ $MESSAGE =~ $JIRA_ISSUE_TAG ]]; then
echo -e "\e[32mGreat, your commit message contains a JIRA issue!\e[0m"
echo -e "\e[31mOh hamburgers ... You forgot to add a JIRA issue number!\e[0m";
Method 2 – This is another very good example to implement to force jira id in each commit message. http://nsbogan.com/tools/2015/06/04/jira-id-in-git-commit-messages
How to replace Changes after the Gerrit review without changing the commit id?
One of the main benefits of code review is the ability to receive and incorporate feedback from other developers without changing the commit-id and review id. With Gerrit, you incorporate these changes by amending the commit. Gerrit uses the CHange-Id to ensure that each iteration of the commit are stored together as patchsets.
The process of modify same commit and commit message on gerrit after patchset creation is pretty straight forward.
Step 1 – Do the required modification in the code based on the review.
Step 2 – Add files using git add commands.
$ git add filename
Step 3 – Command to update/amend the most recent commit.
$ git commit --amend
When amending a commit with git commit –amend, leave the Change-Id line unmodified in the commit message. This will allow Gerrit to automatically update the change with the amended commit.
Step 4 – Gerrit updates the commit under review with your latest changes.
$ git push origin HEAD:refs/for/master
$ git push origin HEAD:refs/for/[BRANCH_NAME]