I hereby claim:
- I am yudhasetiawan on github.
- I am yudha (https://keybase.io/yudha) on keybase.
- I have a public key ASDso1abY7e217cgKTHvITBtWHezu7Zs0SMUCxYcagTjqgo
To claim this, I am signing this object:
Yudha Setiawan yudhasetiawan
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
| { | |
| "abbey": "4c4f56", | |
| "acadia": "1b1404", | |
| "acapulco": "7cb0a1", | |
| "affair": "714693", | |
| "akaroa": "d4c4a8", | |
| "alabaster": "fafafa", | |
| "albescent-white": "f5e9d3", | |
| "algae-green": "93dfb8", | |
| "allports": "0076a3", |
yudhasetiawan
/ Git Commit Message Guidelines.md
Last active
September 20, 2016 04:04
Modification version of some commons best practice commit message guidelines to improve readability.
The commit message plays an important role in revision control systems. They are the first thing other people will see of your commit. Git and related tools work best when following a certain guideline for commit messages. A deeper [introduction on git revision log conventions][a-note-about-git-commit-messages] is helpful to understand the scope. Commit messages should describe what changed, and reference the issue number if the commit closes or is associated with a particular issue.
This leads to more readable messages that are easy to follow when looking through the project history. But also, often commit messages will be used to generate a change log for releases of an application, plugin or code base.
Having commit messages that follow this formatting will prepare your code for distribution, and make formatting consistent.