git log --oneline and --graph - Step-by-Step Execution

Process Flow - git log --oneline and --graph

Start: git log command

↓

Parse --oneline flag

↓

Show each commit as one line

↓

Parse --graph flag

↓

Draw ASCII graph of commit branches

↓

Display combined output

↓

End

The git log command reads commit history, then --oneline shortens each commit to one line, and --graph adds a visual ASCII branch graph.

Execution Sample

Git

git log --oneline --graph

Shows commit history as a simple one-line summary per commit with a branch graph.

Process Table

Step	Action	Evaluation	Result
1	Run git log command	Detect flags --oneline and --graph	Prepare to format output
2	Process --oneline	Shorten each commit to one line with commit hash and message	Each commit shown as: <hash> <message>
3	Process --graph	Generate ASCII graph lines showing branch and merge structure	Graph lines like '*', '|', '/', '\\' added before commit lines
4	Combine graph and oneline output	Merge graph symbols with commit lines	Final output shows graph + one-line commits
5	Display output	Print combined lines to terminal	User sees commit history with branch graph and short commit lines
6	End	No more commits	Command finishes

💡 All commits processed and displayed with graph and oneline format

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
commit_list	Full commit objects	Shortened to one-line summaries	One-line summaries with graph lines prepended	Displayed combined output
graph_lines	Empty	Empty	ASCII graph lines generated	Combined with commit lines
output_lines	Empty	One-line commit lines	Graph + commit lines combined	Printed to terminal

Key Moments - 3 Insights

Why do the commit lines only show a short hash and message?

Because the --oneline flag shortens each commit to one line showing only the abbreviated hash and the commit message, as seen in execution_table step 2.

How does the ASCII graph show branches and merges?

The --graph flag adds ASCII characters like '*', '|', '/', and '\\' before each commit line to visually represent branches and merges, explained in execution_table step 3.

Why are the graph symbols combined with the commit lines?

To show both the commit info and the branch structure together, the graph lines are prepended to the one-line commit summaries, as in execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution table, what is the output after step 2?

A One-line commit summaries with short hash and message

B Full commit details with author and date

C Empty output

D Only ASCII graph lines

💡 Hint

Refer to execution_table row with Step 2 showing the effect of --oneline

At which step are ASCII graph lines generated?

A Step 1

B Step 3

C Step 2

D Step 5

💡 Hint

Check execution_table row for Step 3 describing --graph processing

If you remove --graph, how would the output change?

A Full commit details shown

B No commit messages shown

C No ASCII graph lines, only one-line commits

D Output would be empty

💡 Hint

Consider what execution_table step 3 does and what happens if it is skipped

Concept Snapshot

git log --oneline --graph
- --oneline: shows each commit as one short line (hash + message)
- --graph: adds ASCII art showing branch and merge structure
- Combined output helps visualize commit history simply
- Use together to see a clear, compact branch graph

Full Transcript

The git log command shows commit history. Adding --oneline shortens each commit to one line with a short hash and message. Adding --graph draws an ASCII branch graph showing how commits connect. The command processes these flags step-by-step: first shortening commits, then generating graph lines, then combining both for display. This helps users see a simple, visual summary of their project's commit history with branches and merges clearly shown.