Merge branch 'unstable' into docs/conventional-commits-update

Author: dharapandya85

CONTRIBUTING.md

@@ -117,11 +117,16 @@ Commit contents, in other words, the changes the commit introduce should:
 Example:
 feat(foo)!: introduce breaking change bar
 
+
 For more, see [Conventional Commits v1.0.0](https://www.conventionalcommits.org/en/v1.0.0/) 
 
+`patch-hub` follows the use of [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) wherein you indicate the type of change you're making at the start with a label, followed by a scope (optional, since the project is still small), and then the commit message after a colon. In case the commit is a breaking change, i.e it disrupts existing functionality, please use the `!` symbol before the `:` to indicate as such.
+
+
 Example Commits:
-- `feat: allow provided config object to extend other configs`
-- `docs: correct spelling of CHANGELOG`
+- Breaking change that introduces a feature to `config`: `feat(config)!: allow provided config object to extend other configs`
+- Bug fix to patch parsing logic: `fix(patch): fix incorrect title in patches`
+- Simple change to documentation: `docs: correct spelling of CHANGELOG`
 
 Common prefixes:
 - `feat`: A new feature.