Skip to content

Commit Message Convention & Branch strategy

DongUk Kim edited this page May 15, 2024 · 1 revision

📝 Commit Message Convention

1. Commit Message Rules

  • Before committing:
    1. Perform build tests for the project.
    2. Use Code Spell Checker for typo checks.
Type Description
add: Add new features, package managers, or documentation.
fix: Modify logic, styles, types, functions, components, or libraries.
refactor: Code refactoring (no logic change, typo corrections, variable names, clean code, function abstraction).
test: Add test codes or refactoring test codes.
bug: Fix and complete QA tickets.

2. Branch Naming for Features

Example: 65-feature-epic

Category Task
feature Functionality additions
hotfix Urgent bug fixes and issues that need immediate reflection in the operational branch.
"" More categories to be added as needed.

📈 Branch strategy

image

https://trunkbaseddevelopment.com/