Last active
April 22, 2020 07:19
-
-
Save MatejBransky/d71daba4f8c233282511147cb7275409 to your computer and use it in GitHub Desktop.
Inspects branch name and checks if it contains a Jira ticket number. If yes, commit message will be automatically prepended with it.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
# Check if the COMMIT_EDITMSG file exists (the case was found at GIT GUI) | |
if [ ! -f "$1" ]; then | |
exit | |
fi | |
# | |
# Inspects branch name and checks if it contains a Jira ticket number (i.e. ABC-123). | |
# If yes, commit message will be automatically prepended with [ABC-123]. | |
# | |
# Useful for looking through git history and relating a commit or group of commits | |
# back to a user story. | |
# | |
# | |
# Resources: | |
# - https://gist.github.com/johncmunson/ca02a8027a923a7f4b2f662c67d6528c | |
# - https://gist.github.com/bartoszmajsak/1396344 | |
# - https://stackoverflow.com/questions/34213120/find-branch-name-during-git-rebase | |
# - https://github.com/typicode/husky/issues/311#issuecomment-580237182 | |
# - https://gmurphey.github.io/2013/02/02/ignoring-git-hooks-when-rebasing.html#.XkK1AhNKjOQ | |
# - https://mikemadisonweb.github.io/2018/12/18/git-hook-prepending-commit-message/ | |
# - https://stackoverflow.com/questions/5894946/how-to-add-gits-branch-name-to-the-commit-message | |
# - http://blog.bartoszmajsak.com/blog/2012/11/07/lazy-developers-toolbox-number-1-prepend-git-commit-messages/ | |
# | |
BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD 2>/dev/null) | |
# Ensure BRANCH_NAME is not empty and is not in a detached HEAD state (i.e. rebase). | |
# SKIP_PREPARE_COMMIT_MSG may be used as an escape hatch to disable this hook, | |
# while still allowing other githooks to run. | |
if [ ! -z "$BRANCH_NAME" ] && [ "$BRANCH_NAME" != "HEAD" ] && [ "$SKIP_PREPARE_COMMIT_MSG" != 1 ]; then | |
# supports even JIRA issues with lowercased letters (e.g.: branch name "bugfix/ia-2136" works) | |
PREFIX_PATTERN='[a-zA-Z]{2,5}-[0-9]{1,4}' | |
[[ $BRANCH_NAME =~ $PREFIX_PATTERN ]] | |
PREFIX=${BASH_REMATCH[0]^^} | |
PREFIX_IN_COMMIT=$(grep -c "\[$PREFIX\]" $1) | |
# Ensure PREFIX exists in BRANCH_NAME and is not already present in the commit message | |
if [[ -n "$PREFIX" ]] && ! [[ $PREFIX_IN_COMMIT -ge 1 ]]; then | |
sed -i.bak -e "1s~^~[$PREFIX] ~" $1 | |
fi | |
fi | |
# | |
# Alternative method for finding the branch name | |
# | |
# Note that during a rebase, this will return something like | |
# (no branch, rebasing ABC-123-feature-x) | |
# instead of | |
# HEAD | |
# | |
# BRANCH_NAME=$(git branch | grep '*' | sed 's/* //') | |
# | |
# | |
# Also, don't forget to place this inside package.json if this is part of a node/npm project | |
# | |
# "husky": { | |
# "hooks": { | |
# "prepare-commit-msg": "./prepare-commit-msg.sh $HUSKY_GIT_PARAMS" | |
# } | |
# } | |
# |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment