diff options
| author | Kali Kaneko (leap communications) <kali@leap.se> | 2016-10-03 20:40:03 -0400 |
|---|---|---|
| committer | Kali Kaneko (leap communications) <kali@leap.se> | 2016-10-03 21:48:27 -0400 |
| commit | 5519d02f609a87b0ca47a8e82c116811005b6277 (patch) | |
| tree | eea053d2ff8f99a80b2595119cfae829781135a1 /docs/hooks/leap-commit-template.README | |
| parent | 8cdbf714b905246363221089bbf8579e7c8e020c (diff) | |
[docs] revamp bitmask dev docs
Diffstat (limited to 'docs/hooks/leap-commit-template.README')
| -rw-r--r-- | docs/hooks/leap-commit-template.README | 47 |
1 files changed, 47 insertions, 0 deletions
diff --git a/docs/hooks/leap-commit-template.README b/docs/hooks/leap-commit-template.README new file mode 100644 index 0000000..ce8809e --- /dev/null +++ b/docs/hooks/leap-commit-template.README @@ -0,0 +1,47 @@ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +HOW TO USE THIS TEMPLATE: +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Run `git config commit.template docs/leap-commit-template` or +edit the .git/config for this project and add +`template = docs/leap-commit-template` +under the [commit] block + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +COMMIT TEMPLATE FORMAT EXPLAINED +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +[type] <subject> + +<body> +<footer> + +Type should be one of the following: +- bug (bug fix) +- feat (new feature) +- docs (changes to documentation) +- style (formatting, pep8 violations, etc; no code change) +- refactor (refactoring production code) +- test (adding missing tests, refactoring tests; no production code change) +- pkg (packaging related changes; no production code change) +- i18n translation related changes + +Subject should use imperative tone and say what you did. +For example, use 'change', NOT 'changed' or 'changes'. + +The body should go into detail about changes made. + +The footer should contain any issue references or actions. +You can use one or several of the following: + +- Resolves: #XYZ +- Related: #XYZ +- Documentation: #XYZ +- Releases: XYZ + +The Documentation field should be included in every new feature commit, and it +should link to an issue in the bug tracker where the new feature is analyzed +and documented. + +For a full example of how to write a good commit message, check out +https://github.com/sparkbox/how_to/tree/master/style/git |