Skip to content

Instantly share code, notes, and snippets.

@jplindgren

jplindgren/semantic-branch-names.md

Forked from seunggabi/semantic-branch-names.md
Created January 14, 2023 23:31
Show Gist options
  • Save jplindgren/7de760603c332a970ab59f09e4fe9b0b to your computer and use it in GitHub Desktop.
Save jplindgren/7de760603c332a970ab59f09e4fe9b0b to your computer and use it in GitHub Desktop.
Download ZIP
semantic-branch-names.md
Raw
semantic-branch-names.md

Semantic Branch Names

See how a minor change to your branch name style can make you a better programmer.

Format: <type>/#<issueNumber>-<alias>

Example

feature/#1-init
^------^   ^---^
|          |
|          +---> issue's keyword
|
+-------> Type: or feat, chore, docs, fix, refactor, style, or test.

More Examples:

  • feat or feature: (new feature for the user, not a new feature for build script)
  • fix: (bug fix for the user, not a fix to a build script)
  • docs: (changes to the documentation)
  • style: (formatting, missing semi colons, etc; no production code change)
  • refactor: (refactoring production code, eg. renaming a variable)
  • test: (adding missing tests, refactoring tests; no production code change)
  • chore: (updating grunt tasks etc; no production code change)

References:

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