jira-prepare-conventional-commit-msg

The husky command to add JIRA ticket ID into the scope of conventional commit message if it is missed.

The JIRA ticket ID is taken from a git branch name.

Why?

Installing Jira prepare commit msg hook into your project will mean everyone contributing code to your project will automatically tag each commit with it's associated issue key based off the branch name.

So if your branch name is feature/TEST-123-new-feature, then when you commit with a message "initial commit" it will automatically become "chore(TEST-123): initial commit".

Why would you want this? Well, Jira has many hidden goodies, and this is one of them! If you include an issue key in your commit messages AND you have your deployment pipeline connected to Jira this will unlock many bonus features, such as the Deployments view, Cycle time report, Deployment frequency report and etc.

Additionally, when you use Conventional Commits you will get a nice commit history and clean changelog.

Installation

Install the package using NPM

1npm install husky jira-prepare-conventional-commit-msg --save-dev && npx husky install

For Husky 5:

Execute command

1npx husky add .husky/prepare-commit-msg 'npx jira-prepare-conventional-commit-msg $1'

For Husky 2-4:

Inside your package.json add a standard husky npm script for the git hook

1{
2  "husky": {
3    "hooks": {
4      "prepare-commit-msg": "jira-prepare-conventional-commit-msg"
5    }
6  }
7}

Configuration

Starting with v1.3 you can now use different ways of configuring it:

• jira-prepare-commit-msg object in your package.json
• .jirapreparecommitmsgrc file in JSON or YML format
• jira-prepare-commit-msg.config.js file in JS format

See cosmiconfig for more details on what formats are supported.

package.json example:

1{
2  "jira-prepare-commit-msg": {
3    "jiraTicketPattern": "([A-Z]+-\\d+)",
4    "conventionalCommitPattern": "^([a-z]+)(?:\\(([a-z0-9.,-_ ]+)\\))?!?: ([\\w \\S]+)$",
5    "allowEmptyCommitMessage": false,
6    "ignoredBranchesPattern": "^(master|main|dev|develop|development|release)$",
7    "ignoreBranchesMissingTickets": false
8  }
9}

Supported JIRA ticket pattern

jira-prepare-conventional-commit-msg allows using custom regexp string pattern to search JIRA ticket number.

Pattern ([A-Z]+-\\d+) is currently supported by default.

NOTE: to search JIRA ticket pattern flag i is used: new RegExp(pattern, i')

1{
2  "jira-prepare-commit-msg": {
3    "jiraTicketPattern": "([A-Z]+-\\d+)"
4  }
5}

Allow empty commit message

The commit message might be empty after cleanup or using -m "", jira-prepare-conventional-commit-msg might insert the JIRA ticket number anyway if this flag is set.

1{
2  "jira-prepare-commit-msg": {
3    "allowEmptyCommitMessage": true
4  }
5}

Ignoring branches

Branches can be ignored and skipped by regex pattern string

1{
2  "jira-prepare-commit-msg": {
3    "ignoredBranchesPattern": "^main|develop|(maint-.*)$"
4  }
5}

Moreover, this can be solved by replacing the Husky hook. Put in your prepare-commit-msg file (husky git hook):

1#!/bin/sh
2. "$(dirname "$0")/_/husky.sh"
3
4if [[ "$(git rev-parse --abbrev-ref HEAD)" =~ YOUR_BRANCH_REGEX ]]; then
5npx --no-install jira-prepare-conventional-commit-msg $1
6fi

where YOUR_BRANCH_REGEX e.g. ^(feature|(bug|hot)fix)\/[A-Z]+-[0-9]+$

Silently ignore any branch that does not have a jira ticket in it

Be silent and skip any branch with missing jira ticket

1{
2  "jira-prepare-commit-msg": {
3    "ignoreBranchesMissingTickets": true
4  }
5}

Conventional commit

jira-prepare-conventional-commit-msg natively works with conventional commit.

Examples

If the commit message is fix(test)!: important changes then at result will be fix(test, JIRA-1234)!: important changes.

Additionally, you can customize the conventional commit format with the following setting:

1{
2  "jira-prepare-commit-msg": {
3    "conventionalCommitPattern": "^([a-z]+)(?:\\(([a-z0-9.,-_ ]+)\\))?!?: ([\\w \\S]+)$"
4  }
5}

The above regular expression is the default conventional commit pattern so, if you don't provide this property, jira-prepare-conventional-commit-msg will use this by default.

In the default regular expression, from left to right:

• ([a-z]+) is the commit type.
• (?:\\(([a-z0-9.,-_ ]+)\\))?!? is the commit scope.
• And ([\\w \\S]+) is the commit subject.

With this setting you can change how jira-prepare-conventional-commit-msg reads your custom conventional commit message and rewrites it properly adding the Jira ticket id in the scope.

Examples

You can allow the scope to have capital letters adding A-Z to the regular expression above. If the configuration is:

1{
2  "jira-prepare-commit-msg": {
3    "conventionalCommitPattern": "^([a-z]+)(?:\\(([a-zA-Z0-9.,-_ ]+)\\))?!?: ([\\w \\S]+)$"
4    //                                                ^^^
5    //                 Now we can use capital letters in the conventional commit scope
6  }
7}

and commit message is "test(E2E): some end-to-end testing stuff" then at result will be "test(E2E, JIRA-1234): some end-to-end testing stuff"

Be aware that if you leave the default conventionalCommitPattern value (that it not allows capital letters in the commit scope) in the example above, your resulting message will be "chore(JIRA-1234): test(E2E): some end-to-end testing stuff". Maybe, this is not the result you are expecting and you can have problems using other tools like commitlint.

License

MIT