Standards or rules for commit messages

<aside> 💡 We follow commit standards based on conventional commits, which are enforced using husky and commitlint.

</aside>

Rules to follow git commit:

* Branch management ( rebase )

<aside> 💡 master branch should always be deployable so merge only when feature is fully ready.

</aside>

• How to rebase

* Commit message syntax :

• Details

<type>[optional scope]: <description>
															BLANK LINE
[optional body]
															BLANK LINE
[optional footer(s)]

examples:

1. feat(fix): type short title imperatively

There is no hard rule for body, just write it brief and accurate using present tense

2. feat($browser): onUrlChange event (popstate/hashchange/polling)

Added new event to $browser:

• forward popstate event if available
• forward hashchange event if popstate not available
• do polling when neither popstate nor hashchange available

Breaks $browser.onHashChange, which was removed (use onUrlChange instead)