easyLearn Git Branching#commit-graph#merge#reflog

Practice Git Branching and Recovery

Use a visual Git sandbox to create branches, merge histories, resolve a conflict, and recover a commit by following references.

The Runtime Theory TeamSeptember 25, 20261 min read

Solve it

Solving happens on the judge — come back and mark it done

Sample cases

inCreate two branches from a shared commit and add separate commits

outDraw the commit graph and identify each branch name's target

inMerge branches with and without a conflicting edit

outExplain fast-forward vs merge commit and resolve the conflicting file state

inMove a branch pointer by resetting in the sandbox

outIdentify which commit remains reachable and how reflog-style history can recover it

Complete the linked interactive Git exercises for branch creation, merging, and recovery. After each command, draw the commit graph: commits are snapshots connected by parent links, while branch names move to point at commits.

Pay attention to the difference between changing a branch pointer and deleting the commit object. Practice a fast-forward merge and a divergent merge. In a conflict, inspect the resulting working tree before creating the merge commit.

Do this in the sandbox rather than a repository with important work. Finish by explaining how a reflog can help recover a recently moved reference and why it is not a permanent backup.

One dispatch a week

The trace behind each problem, the tradeoff that explains it, and one technical dispatch per week — no noise.

One technical dispatch per week. No noise.

Not started