Semantic confirmation messages

The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of.

See how a small change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> it's optional

🔭 Example

feat: add widget 
^--^  ^------------^
|     |
|     +-> Abstract in the present tense.
|
+-------> Model: chore, docs, feat, fix, refactor, style, or test.

ProTip! Great commit summaries contain fewer than 50 characters. Place extra information in the extended description.

📡 More examples:

• feat: (new resource for user, not a new resource for build script)
• fix: (bug fix for the user, not a fix for a build script)
• docs: (documentation changes)
• style: (formatting, missing semicolon, etc; no production code change)
• refactor: (formatting, missing semicolon, etc; no production code change)
• test: (add missing tests, refactor tests; no production code change)
• chore: (task update grunts etc; no production code change)

🧠 References:

• https://www.conventionalcommits.org/
• https://seesparkbox.com/foundry/semantic_commit_messages
• http://karma-runner.github.io/1.0/dev/git-commit-msg.html

🔗 Meet me!

• Linkedin: https://www.linkedin.com/in/italo-santos-dev/
• Instagram: https://www.instagram.com/italosantsz/
• Github: https://github.com/dev-italosantos