-
Notifications
You must be signed in to change notification settings - Fork 1
git commit message conventions
David Sklář edited this page Nov 3, 2017
·
1 revision
It's strongly recommended following the Angular team Git Commit Message Conventions.
This convention allows to automate project CHANGELOG processing via grunt release task and grunt-conventional-changelog plugin.
(TYCHO-123) <type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
| type | description |
|---|---|
| feat | feature |
| fix | bug fix |
| docs | documentation |
| style | formatting, typos |
| refactor | refactoring |
| test | when adding missing tests |
| chore | maintain |
Pattern is set via headerPattern option in grunt-conventional-changelog config.
/^(?:(TYCHO-\d+) )?(\w*)(?:\(([\w\$\.\-\*\/ ]*)\))?\: (.*)$/
TYCHO-3817 feat(dashboard): set `z-index`
chore(metalsmith): add `publish` option
Implement `metalsmith-publish` plugin.
chore(bower): add dependencies
Move Compass/Susy from `devDependencies` to `dependencies`.
feat(setting): update `primary` colour theme
Add `$green: #4caf50`.
refactor(dropdown): indentation
- adjust indentation
- remove obsolete code
fix(grunt): change `dist` folder structure
Update sass files path to allow distinguish loading via `includePaths` grunt-sass plugin option.
BREAKING CHANGE: change common sass files path.
Before:
`dist/common/sass`
After:
`dist/sass/common`