git gud - Branch Strategy Bootcamp

Описание

Branch Strategy Bootcamp is a themed challenge pack for git gud that sends you on rotation through three companies, each betting the business on a different branching strategy. You will ship features, patch emergencies, and cut releases exactly the way each team actually works, then prove you can pick the right strategy yourself when nobody hands you the playbook.

This content pack features twelve story-driven Git scenarios built around a fully simulated repository and command-line environment. Each challenge mirrors a real branching workflow decision, wrapped in a narrative that explains why a team chose that strategy, not just which commands to type.

Across your rotation, you will:

• Ship a feature branch and merge it clean at Brightcart, a fast-moving startup practicing GitHub Flow

• Rush a hotfix straight through to a deployable main, no special process required

• Stand up develop and release branches at Ledgerline, a boxed-release accounting suite on Git Flow

• Land a hotfix in both main and develop so a fixed bug never resurrects in the next release

• Keep branches alive for hours instead of days at Meshly, an infrastructure team on Trunk-Based Development

• Rebase onto a moving trunk to keep the history a clean, linear line

• Tag a deploy and read git describe output like an ops dashboard

• Back up an old release with a fix cherry-picked across parallel maintenance branches

Like the base game, Branch Strategy Bootcamp implements Git behavior as faithfully as possible: real branches, real merges, real rebases, and real tag semantics. Nothing here is an abstract puzzle standing in for the genuine commands.

The final challenges drop the training wheels entirely. Given a company's situation and no instructions on which strategy to use, you decide, then execute the full workflow yourself: branch, merge, release, tag, ship.

This DLC is ideal for players who already understand Git basics and want to see how professional teams actually organize their branches, and why the "best" strategy always depends on the team.