{"id":5249,"date":"2018-08-22T14:21:59","date_gmt":"2018-08-22T14:21:59","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/?p=5249"},"modified":"2021-11-17T10:14:30","modified_gmt":"2021-11-17T10:14:30","slug":"enforce-the-jira-issue-id-in-a-git-commit-message","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/enforce-the-jira-issue-id-in-a-git-commit-message\/","title":{"rendered":"Enforce the JIRA issue id in a GIT commit message"},"content":{"rendered":"

\"\"<\/p>\n

Enforce the JIRA issue id in a GIT commit message<\/p>\n

This can be done by using git hooks file location at .git\/hooks\/commit-msg<\/strong>. Following are the 2 way in whcih each Developers can set the Hooks in their developement envioronment.<\/p>\n

Method – 1<\/strong><\/p>\n

[code]# commit-msg.sh
\n#!\/bin\/sh
\n# This hook will make sure that the commit message contains a JIRA issue.
\n#
\n# To enable this hook, rename this file to “.git\/hooks\/commit-msg”.
\n# Make sure to add execution permissions to the file.<\/p>\n

export MESSAGE=$(<$1)
\nexport JIRA_ISSUE_TAG=’ISSUETAG-([0-9]*)’<\/p>\n

if [[ $MESSAGE =~ $JIRA_ISSUE_TAG ]]; then
\necho -e “\\e[32mGreat, your commit message contains a JIRA issue!\\e[0m”
\nexit 0;
\nfi<\/p>\n

echo -e “\\e[31mOh hamburgers … You forgot to add a JIRA issue number!\\e[0m”;
\nexit 1;<\/p>\n

[\/code]<\/p>\n

Method 2 –<\/strong> 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<\/p>\n\n