Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Use this Git commit message template to write better commit messages.
Replace this line with imperative summary
An awesome description of WHY you did this work, not HOW/WHAT it does.
The diff attached to commit should describe implementation (HOW)
well-enough.
# [TICKET-12]
#------------------------------------------------^---------------------^
# 50^ 72^
# 1. Summary should be imperative (not past tense), 50 characters or
# less, and not end with a period.
#
# 2. Description of commit should explain WHY a change was made and
# lines should be wrapped to 72 characters.
#
# 3. Optionally, reference a ticket number. If needed, uncomment and
# go to town.
#
# For more tips:
# http://chris.beams.io/posts/git-commit
# https://github.com/erlang/otp/wiki/writing-good-commit-messages#do
#
To_Setup_Do(){ #...
cd /tmp/
curl -O https://gist.githubusercontent.com/RichardBronosky/beacdea6106de0d0c7d36fbaf625139e/raw/setup.sh
bash setup.sh
}
curl https://gist.githubusercontent.com/RichardBronosky/beacdea6106de0d0c7d36fbaf625139e/raw/.gitmessage > ~/.gitmessage
git config --global --replace-all commit.template '~/.gitmessage'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment