guisalva

Git Branch Naming Cheat Sheet

A quick reference for creating clear, consistent, and readable Git branch names.

Basic Rules

• Lowercase and hyphen-separated — use lowercase and - to separate words.
  • feature/new-login
  • bugfix/header-styling

guisalva

Types

• feat Commits, that adds or remove a new feature
• fix Commits, that fixes a bug
• refactor Commits, that rewrite/restructure your code, however does not change any API behaviour
• perf Commits are special refactor commits, that improve performance
• style Commits, that do not affect the meaning (white-space, formatting, missing semi-colons, etc)
• test Commits, that add missing tests or correcting existing tests
• docs Commits, that affect documentation only
• build Commits, that affect build components like build tool, ci pipeline, dependencies, project version, ...
• ops Commits, that affect operational components like infrastructure, deployment, backup, recovery, ...