
Product
Announcing Bun and vlt Support in Socket
Bringing supply chain security to the next generation of JavaScript package managers
@healthmatch/jira-prepare-commit-msg
Advanced tools
Husky Git hook to add JIRA ticket ID into the commit message
The husky command to add JIRA ticket ID into the commit message if it is missed.
The JIRA ticket ID is taken from a git branch name.
Install the package using NPM
npm install husky jira-prepare-commit-msg --save-dev
Inside your package.json add a standard husky npm script for the git hook:
{
"husky": {
"hooks": {
"prepare-commit-msg": "jira-prepare-commit-msg"
}
}
}
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 formatjira-prepare-commit-msg.config.js file in JS formatSee cosmiconfig for more details on what formats are supported.
package.json example:{
"jira-prepare-commit-msg": {
"messagePattern": "[$J]\n$M",
"jiraTicketPattern": "([A-Z]+-\\d+)",
"commentChar": "#",
"isConventionalCommit": false
}
}
jira-prepare-commit-msg supports special message pattern to configure where JIRA ticket number will be inserted.
$J will be replaced on JIRA ticket number$M will be replaced on commit message.Pattern [$J]\n$M is currently supported by default.
{
"jira-prepare-commit-msg": {
"messagePattern": "[$J]\n$M"
}
}
[$J] $M[$J]-$M$J $MNOTE: the supplied commit message will be cleaned up by strip mode.
jira-prepare-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')
{
"jira-prepare-commit-msg": {
"jiraTicketPattern": "([A-Z]+-\\d+)"
}
}
Git uses # by default to comment lines in the commit message. If default char was changed jira-prepare-commit-msg can allow set it.
{
"jira-prepare-commit-msg": {
"commentChar": "#"
}
}
jira-prepare-commit-msg supports conventional commit. To insert JIRA
ticket number to the description set the following setting:
{
"jira-prepare-commit-msg": {
"isConventionalCommit": false
}
}
NOTE: For description will be applied messagePattern
If the configuration is:
{
"jira-prepare-commit-msg": {
"messagePattern": "[$J] $M",
"isConventionalCommit": false
}
}
and commit message is fix(test)!: important changes then at result will be fix(test)!: [JIRA-1234] important changes
MIT
FAQs
Husky Git hook to add JIRA ticket ID into the commit message
We found that @healthmatch/jira-prepare-commit-msg demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Product
Bringing supply chain security to the next generation of JavaScript package managers

Product
A safer, faster way to eliminate vulnerabilities without updating dependencies

Product
Reachability analysis for Ruby is now in beta, helping teams identify which vulnerabilities are truly exploitable in their applications.