In this lesson, you will learn how to use the Git graph view to visually map out how your project’s history branches and converges over time.
While git log gives you a chronological list of changes, it can become difficult to follow the "story" of your project when you have multiple branches working in parallel. Git provides a powerful flag that draws a simple ASCII-based diagram directly in your terminal, showing you exactly where branches split off and where they merge back into your main line of development.
Enabling the Graph View
To see this visualization, append the --graph flag to your git log command. To make the output cleaner and easier to read, developers typically combine it with --oneline and --all:
git log --graph --oneline --all
When you run this, you will see a vertical line on the left side of your terminal representing your commit history. You will notice:
- Asterisks (
*): These represent individual commits. - Vertical lines (
|): These show the path of a branch. - Diagonal lines (
/or\): These indicate where a branch diverged from another or where a merge occurred.
Interpreting the Flow
Imagine you are working on a feature-login branch. When you run the graph command, you might see a line fork away from your main branch. This allows you to visually confirm that your feature work is safely isolated. Once you merge that feature back into main, the graph will show the lines converging, providing a clear snapshot of your project's evolution.
This view is your best friend when you need to understand the "topology" of your repository. Instead of just reading text, you are seeing the literal structure of your work, making it significantly easier to identify exactly which commit belongs to which branch and when specific features were integrated.
Key Takeaway: The --graph flag transforms your commit history into a visual roadmap, allowing you to trace the lifecycle of your branches and confirm exactly when and how changes were merged into your project.