bashANYgitbisectdebugging
bash
git bisect start <bad_commit> <good_commit>Fastest way to launch a bisect session when both endpoints are already known.
Git Bisect, Cherry-pick, and Submodule Cheat Sheet
Advanced workflows for regression hunting, selective commit transfer, and repository dependency management.
Export
Copy the compact sheet, download it, or print it.
Download
`D` dense toggle · `C` copy all
Bisect Workflows
Use binary search to identify the commit that introduced a bug or behavior change.
bashANYgitbisectdebugging
bash
git bisect goodBisect uses your good/bad classification to narrow the search range.
bashANYgitbisectdebugging
bash
git bisect badEach classification halves the remaining search space.
bashANYgitbisectautomationdebugging
bash
git bisect run ./test-regression.shPowerful for deterministic regressions where a test script can return success/failure automatically.
bashANYgitbisectcleanup
bash
git bisect resetAlways reset at the end so you are no longer on a temporary bisect-selected revision.
bashANYgitbisectskip
bash
git bisect skipUseful when a revision does not build or cannot be meaningfully tested.
Cherry-pick Workflows
Copy selected commits across branches safely.
bashANYgitcherry-pickworkflow
bash
git cherry-pick <commit_sha>Common for backports, hotfixes, or selectively transferring changes across branches.
bashANYgitcherry-pickworkflow
bash
git cherry-pick <sha1> <sha2> <sha3>Useful when the commits are not contiguous in history but all need to be transferred.
bashANYgitcherry-pickrange
bash
git cherry-pick <start_sha>^..<end_sha>Common syntax for selecting a continuous segment of commits.
bashANYgitcherry-pickmergemainline
bash
git cherry-pick -m 1 <merge_commit_sha>Like revert of a merge, cherry-picking a merge requires selecting the mainline parent.
bashANYgitcherry-pickcontinueconflicts
bash
git cherry-pick --continueCherry-pick uses the same style of conflict lifecycle as rebase and revert.
bashANYgitcherry-pickabort
bash
git cherry-pick --abortUse when conflicts are too messy or you decide not to port the change.
Submodule Workflows
Initialize, update, sync, and maintain submodule-based repositories.
bashANYgitsubmodulestatus
bash
git submodule status --recursiveUseful for understanding whether submodules are initialized, detached, or out of sync.
bashANYgitsubmoduleclone
bash
git clone --recurse-submodules <repo_url>Saves an extra initialization step after clone for repositories that depend on submodules.
Update submodules to their tracked remote branches
Fetch and move submodules according to configured tracking branches.
bashANYgitsubmoduleupdateremote
bash
git submodule update --remote --recursiveUseful when submodules are meant to follow upstream branch tips rather than staying pinned until manually updated.
bashANYgitsubmoduleforeach
bash
git submodule foreach --recursive 'git status --short'Great for auditing or applying common operations across many submodules.
bashANYgitsubmodulesync
bash
git submodule sync --recursiveImportant after changing submodule remote URLs in `.gitmodules`.
bashANYgitsubmoduleremove
bash
git rm path/to/submoduleModern Git handles most removal cleanup well, but you should still review `.gitmodules` and config state afterward.
More in Git Advanced
Git Stash, Worktree, and Clean Cheat Sheet
Temporary work preservation, multi-worktree workflows, cleanup commands, and conflict-resolution reuse.
Git Reset, Revert, and Restore Cheat Sheet
Understand the differences between reset, revert, and restore and use the right recovery command safely.
Git Reflog and Recovery Cheat Sheet
Recover commits, branches, and work after resets, rebases, deletes, and mistaken force updates.
Git Rebase Cheat Sheet
Advanced rebase commands, interactive workflows, conflict handling, and branch-transplant patterns.
Git Advanced Cheat Sheet
Advanced Git commands and workflows for rewriting history, recovering commits, debugging regressions, working with multiple trees, and maintaining repositories.