Skip to content

Instantly share code, notes, and snippets.

@josephgoksu

josephgoksu/branch-naming-convention.md

Last active April 27, 2022 08:53
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save josephgoksu/5fff3f6ef7674f0401b1cc9a6191b6ed to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save josephgoksu/5fff3f6ef7674f0401b1cc9a6191b6ed to your computer and use it in GitHub Desktop.
Download ZIP
Git Rules
Raw
branch-naming-convention.md

Git Branch Naming Conventions

<type>/<name>

<type>

bug    - Code changes linked to a known issue.
feature - New feature.
relase - New Release.
improvement - Improvements of the current code or feature
fix/patch - fixes to the codebase.
hotfix - Quick fixes to the codebase.
misc   - other miscellaneous stuff
tests  -  everything about test related
experimental - every experimental reseach (will never be merged).

<name>

Always use dashes to seperate words, and keep it short.

Suffix <JIRA_NO> (Optional)

Commit message convention

<action-verb> <explanation>
<description (optional)>
Example
fix exported JS code from the data-click attribute
On scene reopening, path strings were manipulated by the pathHandler method. We had to ignore paths coming from JS code in data-click. A RegExp check now filters which paths should be manipulated.

Branch Examples

release/v3.1.4
feature/new-onboarding-screen
feature/new-unicorn-emoji-SV1002
hotfix/dockerfile-base-image
bug/login-ie
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment