# Semantic Commit Messages

Format: `<type>(<jira_id>): <subject>`

`<jira_id>` is optional

## Example

```
feat(URUS-1): add hat wobble
^--^  ^---^   ^------^
|     |        |
|     |        +-> Summary in present tense
|     |        
|     +-> JIRA ID.
|
+-------> Type: chore, docs, feat, fix, refactor, style, or test.

```

More Examples:

- `feat`: (new feature for the user, not a new feature for build script)
- `fix`: (bug fix for the user, not a fix to a build script)
- `docs`: (changes to the documentation)
- `style`: (formatting, missing semi colons, etc; no production code change)
- `refactor`: (refactoring production code, eg. renaming a variable)
- `test`: (adding missing tests, refactoring tests; no production code change)
- `chore`: (updating grunt tasks etc; no production code change)


# Branch Naming Rules

Format: `<type>/<jira_id>-<short-description>`

`short-description` is optional

Type: features, bugs, hotfixs

Example: `features/URUS-1`