Skip to content

Instantly share code, notes, and snippets.

@johnstew

johnstew/git-commit-prefixes

Forked from indexzero/git-commit-prefixes
Last active April 1, 2024 03:43
Show Gist options
  • Star 30 You must be signed in to star a gist
  • Fork 6 You must be signed in to fork a gist
  • Save johnstew/941676d525271359a4b2d7f1bf2cb421 to your computer and use it in GitHub Desktop.
Save johnstew/941676d525271359a4b2d7f1bf2cb421 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
git-commit-prefixes
[test]: Update test/* files
[dist]: Changes to submodules, version bumps, updates to package.json
[minor]: Small changes
[doc]: Updates to documentation
[fix]: Bug fixes
[bin]: Update binary scripts associated with the project
[refactor]: Refactor of existing code
[nit]: Small code review changes mainly around style or syntax
[feat]: New features
// Usage
fix: closes #9, fix path issue
nit: swap let for const
doc: added usage section to README.md
@medvedev125
Copy link

medvedev125 commented May 29, 2023 •
edited

IMHO, it's not relevant. We already have The Conventional Commits specification: https://www.conventionalcommits.org/en/v1.0.0/
where next commit prefixes are mentioned :

[fix]:
[feat]: 
[build]:
[chore]:
[ci]:
[docs]:
[style]:
[refactor]:
[perf]:
[test]:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment