Scribd
Upload
7 views1 page

Training Point System - ?

Uploaded by

7xt9s9cv6g
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views1 page

Training Point System - ?

Uploaded by

7xt9s9cv6g
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Git Naming Convention Guide

Introduction
Consistent and meaningful naming conventions for Git branches and commits contribute
to a more organized and understandable version control history. This guide outlines
the recommended naming conventions for branches and commits.

Branch Naming Convention


Feature Branches
Feature branches should be created for each new feature or enhancement.

Format: feature/<task-number>-<short-description>

Example: feature/123_user_authentication

Bugfix Branches
Bugfix branches address and fix specific issues in the codebase.

Format: fix/<issue-number>-<short-description>

Example: fix/123_fix_login_issue

Release Branches
Release branches are created for preparing a new release.

Format: release/<version-number>

Example: release/1.0.0

Hotfix Branches
Hotfix branches address critical issues in the production environment.

Format: hotfix/<issue-number>-<short-description>

Example: hotfix/456-fix-security-vulnerability

Commit Message Convention


Commit Types
ADD : Added New feature for the user.
CHG : Changed feature for the user.
FIX : Fixed Bug fix.
UPDATE : Updated feature for the user.

You might also like