Visualizing Branches

What

A repository’s commit history is represented as a commit graph. Visualizing this graph is key to understanding how different lines of features branch off from one another and where they share a common ancestor.

How

In text-based diagrams, letters represent individual commits, and lines indicate their parentage. Commits are chronological from left to right:

       G - H    feature_a
      /
A - B - C - D   main
  \
   E - F        feature_b

In the diagram above:

main contains commits A, B, C, and D. The tip of the branch is D.
feature_a branches off from commit C. It contains commits A, B, C, G, and H. The tip of this branch is H.
feature_b branches off from commit B. It contains commits A, B, E, and F. The tip of this branch is F.
Commit C is the common ancestor where feature_a split from main.

Why

Because multiple developers can branch off from different points in a project’s timeline simultaneously, histories quickly diverge. Visualizing these splits (and their eventual merges) helps you understand the relationships between different lines of code, navigate historical conflicts, and safely merge changes back together.

Summary

Reading commit graphs from left to right helps you identify branch points, track independent feature lines, and locate common ancestor commits.