Workflows

Release Branch Workflow

Explain when to cut a release branch, when to freeze features, and how to flow fixes back to main.

Scenario

Explain when to cut a release branch, when to freeze features, and how to flow fixes back to main.

Suggested sequence

  1. Cut a release branch from a stable mainline
  2. Accept only release-related fixes
  3. Merge final fixes back into the mainline

Why this order is safer

The value of a workflow usually comes less from a single command and more from fixing the order of observation, action, and recovery.

Related commands

This topic makes more sense alongside commands such as git fetch, git log, git diff, git merge, git rebase, or git cherry-pick.

Related Reads

fetch vs pull

Explains why fetch-first workflows are often more controllable than pulling directly.

Feature Branch Collaboration

A practical feature-branch workflow for day-to-day teamwork, from cutting the branch and syncing main to cleaning the stack before review.

Sync Before Review

Sync your branch with main before opening review so reviewers see current, focused diffs instead of stale base noise.

PreviousHotfix and Urgent Fixes

Handle urgent fixes on a stable base, ship the smallest repair possible, and then flow that repair back into the branches that still need it.

NextBackporting with Cherry-pick

Backport precise fixes onto maintenance branches without merging an entire feature branch.