Foray / GitGit roadmap From the mental model of the four trees to branching workflows, history surgery, hooks and large repositories: the version control every engineer needs, with the recovery recipes for when it goes wrong.
12 topics · 68 nodes · 67 covered · 0 partly · 1 planned · updated 2026-10-17
Sign in with your Mycelium account to see which nodes you have finished.
Show Whole map Gaps only 1. Core
The mental model Git makes sense once you can picture where your changes live. Learn the places first, the commands second.
3 / 3 covered
What Git is Covered The remote repository Covered Working directory, index and repository Covered 2. Core
First steps Set up, commit, look around and keep junk out.
6 / 6 covered
Installing and configuring Covered The art of the commit Covered Keeping junk out Covered Saving progress Covered Looking around Covered A practice sandbox optional Covered 3. Core
Branches and collaboration Work in isolation, then bring changes together with other people.
6 / 6 covered
Working in isolation Covered The golden rule Covered Merge conflicts Covered Syncing with the team Covered Pull requests Covered Line endings and .gitattributes Covered 4. Core
Undoing and recovering Almost nothing in Git is lost. Learn the way back.
7 / 7 covered
Fix the last commit Covered Undo a pushed commit Covered git reset modes Covered Incident playbook Covered Throw away uncommitted work Covered Stash Covered The reflog and bad rebases Covered 5. Recommended
Branching workflows A team agrees how branches are used. Pick one that fits how you ship.
7 / 7 covered
Centralised and feature-branch workflows Covered GitFlow pick one Covered The forking workflow pick one Covered Choosing a strategy Covered GitHub Flow pick one Covered GitLab Flow pick one Covered Trunk-based development pick one Covered 6. Core
Merging and rebasing Two ways to combine history, with different trade-offs.
5 / 5 covered
What each one actually does Covered Interactive rebase Covered Resolving complex conflicts Covered Rebasing Covered Merge strategies and undoing merges Covered 7. Recommended
History and investigation Use history as a tool: find who, when and why.
8 / 8 covered
git log power usage Covered git bisect Covered Tags and releases Covered Revision syntax Covered git blame and git show Covered git cherry-pick Covered Authors, co-authors and statistics optional Covered Patches by email optional Covered 8. Recommended
Configuration and tools Make Git comfortable for daily use.
5 / 5 covered
Ignoring more precisely Covered GUIs and editor integration optional Covered SSH and Git Covered Configuration for real life Covered Quick reference Covered 9. Recommended
Team policy and automation Make the safe path the default for everyone.
6 / 6 covered
Git hooks Covered Signed commits and tags Covered Code-review conventions and PR templates Covered Server-side hooks and branch protection Covered Commit conventions in CI Covered Merge queues and rulesets optional Covered 10. Optional
How Git works inside Optional, but it explains every strange behaviour.
4 / 4 covered
The object model Covered How the four trees really work Covered Refs, HEAD and the packfile Covered git archive and git bundle Covered 11. Optional
Large and complex repositories Scale beyond a single small repository.
7 / 8 covered
git worktree Covered Monorepos Covered git filter-repo Covered Migrating to Git Covered Submodules and subtrees Covered Large files and Git LFS Covered Splitting and merging repositories Covered Jujutsu, Sapling and Mercurial pick one Planned 12. Recommended
Git in delivery Where version control meets pipelines and releases.
3 / 3 covered
CI/CD triggered by Git Covered GitOps Covered Releases and versioning Covered © 2026 Konstantinos Maglaras
