Git Commit Guidelines

  • fix: A bug fix

  • feat: The new feature you're adding to a particular application

  • build: Build related changes (eg: npm related/ adding external dependencies)

  • chore: Regular code maintenance. A code change that external user won't see (eg: change to .gitignore file or .prettierrc file)

  • docs: Everything related to documentation

  • style: Feature and updates related to styling

  • refactor: Refactoring a specific section of the codebase. A code that neither fix bug nor adds a feature. (eg: You can use this when there is semantic changes like renaming a variable/ function name)

  • perf: A code that improves performance

  • test: Everything related to testing. Adding new test or making changes to existing test

  • use imperative, present tense (eg: use "add" instead of "added" or "adds")

  • don't use dot(.) at end

  • don't capitalize first letter

  • fix type commits should be translated to PATCH releases. feat type commits should be translated to MINOR releases. Commits with BREAKING CHANGE in the commits, regardless of type, should be translated to MAJOR releases.

More from UNj
All posts