Quick examples

• feat: New feature
• fix(scope): Bug in scope
• feat!: Breaking change / feat(scope)!: rework API
• chore(deps): Update dependencies

Commit types

• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Changes which doesn't change source code or tests e.g. changes to the build process, auxiliary tools, libraries
• docs: Documentation only changes
• feat: Add or remove a feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that neither fixes a bug nor adds a feature
• revert: Revert something
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

Version bumps

• fix → patch version bump (1.0.0 → 1.0.1)
• feat → minor version bump (1.0.0 → 1.1.0)
• breaking changes (! or BREAKING CHANGE:) → major version bump (1.0.0 → 2.0.0)

Commit example	Bump type	Resulting version	Notes
fix: correct minor typo	Patch	1.0.0 → 1.0.1	For bug fixes
feat: add user login	Minor	1.0.0 → 1.1.0	Adds new functionality
feat!: overhaul API	Major	1.0.0 → 2.0.0	Breaking change (!)
refactor: cleanup utils	None	–	No version bump
docs: update README	None	–	No version bump

Reminders

• Put newline before extended commit body
• More details at conventionalcommits.org