-
-
Save scwebd/ef4d80cf59f704cbcb6acf4ca28f1ab9 to your computer and use it in GitHub Desktop.
This commit message template helps you write great commit messages and enforce it across teams.
This file contains hidden or 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
| # Type(<scope>): <subject> | |
| # <body> | |
| # <footer> | |
| # Type should be one of the following: | |
| # * feat (new feature) | |
| # * fix (bug fix) | |
| # * docs (changes to documentation) | |
| # * style (formatting, missing semi colons, etc; no code change) | |
| # * refactor (refactoring production code) | |
| # * test (adding missing tests, refactoring tests; no production code change) | |
| # * chore (updating grunt tasks etc; no production code change) | |
| # Scope is just the scope of the change. Something like (admin) or (teacher). | |
| # Subject should use impertivite tone and say what you did. | |
| # The body should go into detail about changes made. | |
| # The footer should contain any JIRA (or other tool) issue references or actions. | |
| # For a full example of how to write a good commit message, check out | |
| # https://github.com/sparkbox/how_to/tree/master/style/git | |
| # --------------------------------------------------------------------------------- | |
| # Jira Issue Processing | |
| # ISSUE_KEY #comment This is a comment | |
| # ISSUE_KEY #done | |
| # --------------------------------------------------------------------------------- |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment