Branch Workflow

Branch Workflow Patterns

Reference patterns for branch naming, validation, and protection.

Branch Naming Convention

{type}/{ticket-id}-{description}

Branch Types

Description Guidelines

• Use lowercase with hyphens
• Keep short but descriptive
• No spaces or special characters

Protected Branches

These branches are PROTECTED - never commit directly:

Branch Validation

Check Current Branch

git branch --show-current

Validate Not Protected

const PROTECTED = ['main', 'master', 'production', 'staging', 'develop'];
const current = getCurrentBranch();
if (PROTECTED.includes(current.toLowerCase())) {
  throw new Error(`Cannot operate on protected branch: ${current}`);
}

Extract Ticket ID

// Pattern: type/TICKET-123-description
const match = branchName.match(/^[a-z]+\/([A-Z]+-\d+)/);
const ticketId = match ? match[1] : null;

PR Target Rules

NEVER target main/master directly from feature branches.

Branch Lifecycle

1. Create: Branch from staging/develop
2. Develop: Make changes, commit frequently
3. Push: Push to remote
4. PR: Create PR targeting staging
5. Review: Address feedback
6. Merge: Squash or merge to staging
7. Delete: Remove merged branch

Commands Reference

Create Branch

git checkout staging
git pull origin staging
git checkout -b feature/TICKET-123-description

Check Remote Tracking

git branch -vv

Push New Branch

git push -u origin feature/TICKET-123-description

Delete Merged Branch

# Local
git branch -d feature/TICKET-123-description

# Remote
git push origin --delete feature/TICKET-123-description

Anti-Patterns

• Committing directly to main/master
• Branches without ticket IDs (when applicable)
• Long-lived feature branches (merge frequently)
• Branches with spaces or special characters
• Multiple developers on same branch without coordination

Converted and distributed by TomeVault — claim your Tome and manage your conversions.