Lines Matching +full:commit +full:- +full:message

8 3. Create a new branch (`git checkout -b new-branch`)
10 5. Commit your changes (`git commit -am "your message"`)
12  [conventional changelog format][conventional-changelog-format], so that we can
13  easily update the `CHANGELOG.md` using [clog][clog-cli].
16  * Format your commit subject line using the following format:
17    `TYPE(COMPONENT): MESSAGE` where `TYPE` is one of the following:
18     - `feat` - A new feature
19     - `imp` - An improvement to an existing feature
20     - `perf` - A performance improvement
21     - `docs` - Changes to documentation only
22     - `tests` - Changes to the testing framework or tests only
23     - `fix` - A bug fix
24     - `refactor` - Code functionality doesn't change, but underlying structure
26     - `style` - Stylistic changes only, no functionality changes
27     - `wip` - A work in progress commit (Should typically be `git rebase`'ed
29     - `chore` - Catch all or things that have to do with the build system, etc.
30     - `examples` - Changes to an existing example, or a new example
33    Can be omitted if commit applies globally
35 7. `git rebase` into concise commits and remove `--fixup`s
36    (`git rebase -i HEAD~NUM` where `NUM` is number of commits back)
37 8. Push your changes back to your fork (`git push origin $your-branch`)
44 * Ensure that you update the copyright dates, if necessary (e.g. `2014, 2016` ->
45   `2014, 2016-2017`)
48 [clog-cli]: https://github.com/clog-tool/clog-cli "clog-tool/clog-cli"
50 [conventional-changelog-format]: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#…