===========================================================================================
Make sure your commit message looks like:

  {TAG}:({FEATURE}) {SHORT_DESCRIPTION} {ISSUE_ID}

  {LONG_DESCRIPTION}

Where:
  TAG => Any of the following :
  - BLD: change related to build scripts
  - FIX: bugfixes, hotfixes.
  - BUG: alias for bugfixes, hotfixes.
  - DOC: documentation
  - FEAT: features new features
  - ENH: Performance enhancements, not captured in features
  - REF: maintenance commit (refactoring, etc.)
  - STY: style fix (whitespaces, typos)
  - TST: addition or modification of tests

  FEATURE => Useful to identify commits related to a given feature. Optional.
  SHORT_DESCRIPTION => A very short description
  ISSUE_ID => (Optional). Provide one if you have it example DE12121
  LONG_DESCRIPTION => (Optional). A longer description of the commit. You can use markdown
  to provide some nice formatting

IMPORTANT:
- The maximum length of the message should never be more than [SUBJECT_LIMIT] characters
- Messages starting with `Revert` or `Merge` will be considered valid commits

Example:
  $ git commit
  FIX: (Bamboo Issues) Fix Bamboo Build DE1012
  Fix bug on build while installing
  == OR ==
  In one line
  $ git commit -m "FIX: (Bamboo Issues) Fix Bamboo Build DE1012"
===========================================================================================