# Git commit message format

`<type>`{`<scope>`):`<all lowercase message>`

- space after smicolons for subject text

feat(home): add deal component
fix(about): fix bullet point bug
perf(booking): optimize booking script execution
refactor(contact): change font-weight to improve ux
style(home) – adjust indentation
docs(booking) – add params for booking script
chore(gulp) – add sass compilation task

**where**

## Type `<type>`

1. feat –  new feature/page (things which need to implement as new)

  a. eg. add deal pgae, add 3 new buttons, add deals in home page, etc

2. fix – bug fix (issues, bug, error, eception which happens on top of existing features or page)

 a. eg. font-icon does not show properly, css break after AEM packaging

3. docs – documentation code changes

 a. eg. JSDoc comments

4. style – code beautification (any changes that does not affect any of the code parsing)

 a. eg. formatting alignment, missing semi-colons, indentation, etc)

5. perf – performance optimization (any changes which make code or rendering faster and better)

 a. eg. optimize javascript code to have better execution, optimize html ot have better painting, optimize css for effective rendering

6. refactor – code or ux refactoring (any changes which does not represent feat or bug fix or perf)

 a. eg. adding or removing code to make UI rearrangement, better UX

7. test – unit or e2e test
8. chore – build script (any changes related to bower or gulp)

## Scope `<scope>`

Scope will be the name of work scope/page.

eg. home, deals, discover, booking, offers, about, contact, gulp(chore), bower(chore)

## Subject `<subject>`

1. use present tense "change, add, improve, remove"
2. all lowercase text
3. no dot "." at the end of the sentence
4. include JIRA ticket at the end with hash prefix (#GBB-8)