git log --oneline and --graph - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the git log --oneline command do?

It shows the commit history in a short format, displaying each commit on one line with its abbreviated commit ID and commit message.

beginner

What is the purpose of the --graph option in git log?

It adds a visual ASCII graph to the commit history output, showing the branching and merging structure of the commits.

intermediate

How do --oneline and --graph work together in git log?

They combine to show a compact, one-line-per-commit history with a visual graph of branches and merges, making it easier to understand the commit structure at a glance.

beginner

What does a vertical line (|) in the git log --graph output represent?

It represents a branch line showing the path of commits in a branch.

intermediate

Why is using git log --oneline --graph helpful when working with multiple branches?

Because it visually shows how branches diverge and merge, helping you understand the project history and relationships between commits quickly.

What does the --oneline option do in git log?

A Shows the commit history in reverse order

B Shows the full commit message with details

C Shows each commit in a single line with abbreviated ID and message

D Shows only the commit IDs without messages

The --oneline option condenses each commit to one line showing a short ID and message.

What visual element does git log --graph add to the output?

A A color-coded timeline

B A list of changed files

C A summary of commit authors

D An ASCII graph showing branches and merges

The --graph option adds an ASCII graph to visualize branches and merges.

Which command shows a compact commit history with branch structure?

A git status

B git log --oneline --graph

C git diff

D git branch

git log --oneline --graph shows a short commit list with a visual graph of branches.

In git log --graph, what does a '*' symbol represent?

A A commit point

B A branch name

C A merge conflict

D A deleted file

The '*' symbol marks a commit in the graph output.

Why might you use git log --oneline --graph instead of just git log?

A To see a simpler, visual summary of commits and branches

B To edit commit messages

C To delete old commits

D To push changes to remote

This command helps you quickly understand commit history and branch structure visually.

Explain how git log --oneline --graph helps you understand a project's commit history.

Think about how a simple list and a visual graph together improve clarity.

Describe the meaning of the symbols and lines you see in the output of git log --graph.

Focus on how the ASCII characters map to branches and commits.

Practice

1. What does the git log --oneline command do?

easy

A. Displays the full commit message for each commit

B. Shows each commit in a short, one-line format

C. Shows only the commit hashes without messages

D. Lists all branches in the repository

Solution

1. Step 1: Understand the purpose of --oneline

   The --oneline option shortens each commit to one line showing the commit hash and a brief message.

2. Step 2: Compare options

   Shows each commit in a short, one-line format correctly describes this behavior. Other options describe different commands or incorrect outputs.

3. Final Answer:

   Shows each commit in a short, one-line format -> Option B

4. Quick Check:

   --oneline = short commit summary [OK]

Hint: Remember: --oneline means one line per commit [OK]

Common Mistakes:

• Thinking it shows full commit messages
• Confusing it with branch listing
• Assuming it hides commit messages

2. Which of the following is the correct syntax to show a graphical commit history with short commit lines?

easy

A. git log --oneline --graph

B. git log --graph --one-line

C. git log --graph --short

D. git log --one-line --graph

Solution

1. Step 1: Identify correct options for short and graph

   The correct options are --oneline for short commits and --graph for graphical display.

2. Step 2: Check syntax correctness

   git log --oneline --graph uses the correct flags. git log --graph --one-line, git log --graph --short, and git log --one-line --graph use invalid flags.

3. Final Answer:

   git log --oneline --graph -> Option A

4. Quick Check:

   Use --oneline and --graph together [OK]

Hint: Use --oneline and --graph exactly as flags [OK]

Common Mistakes:

• Using --one-line instead of --oneline
• Using --short which is invalid
• Reversing flag order

3. Given this command: git log --oneline --graph, what will the output show?

medium

A. A graphical tree of commits with short commit messages

B. A list of commits with full messages and no branch structure

C. Only the commit hashes without messages or graph

D. A list of branches and tags in the repository

Solution

1. Step 1: Understand combined flags effect

   The --oneline flag shortens commit info, and --graph adds a visual graph showing branches and merges.

2. Step 2: Match output description

   A graphical tree of commits with short commit messages correctly describes a graphical tree with short commit lines. Other options describe outputs missing graph or messages or unrelated info.

3. Final Answer:

   A graphical tree of commits with short commit messages -> Option A

4. Quick Check:

   --graph + --oneline = graph with short commits [OK]

Hint: Graph shows branches; oneline shortens commits [OK]

Common Mistakes:

• Expecting full commit messages
• Thinking graph shows branches only without commits
• Confusing with branch or tag listing

4. You ran git log --oneline --graph but see no graph lines. What is the likely cause?

medium

A. Your terminal does not support Unicode characters

B. You ran the command outside a git repository

C. You have only one commit with no branches or merges

D. You forgot to add the --decorate flag

Solution

1. Step 1: Understand when graph lines appear

   The graph lines show branch and merge structure. If there is only one commit and no branches, no graph lines appear.

2. Step 2: Evaluate other options

   Your terminal does not support Unicode characters is unlikely because graph uses simple characters. You forgot to add the --decorate flag is unrelated; --decorate adds refs, not graph lines. You ran the command outside a git repository would cause an error, not empty graph.

3. Final Answer:

   You have only one commit with no branches or merges -> Option C

4. Quick Check:

   No branches = no graph lines [OK]

Hint: Graph needs multiple commits with branches [OK]

Common Mistakes:

• Assuming --decorate controls graph lines
• Thinking terminal Unicode breaks graph
• Running command outside repo causes error, not empty graph

5. You want to visualize a complex branch history with merges and short commit messages. Which command best helps you?

hard

A. git log --graph --patch

B. git log --oneline --decorate

C. git log --stat --oneline

D. git log --oneline --graph --all

Solution

1. Step 1: Identify flags for visualization and completeness

   --graph shows branch structure, --oneline shortens commits, and --all includes all branches.

2. Step 2: Compare options

   git log --oneline --graph --all combines all needed flags for a full, clear view. git log --oneline --decorate lacks graph, so no branch lines. git log --graph --patch shows patches, which is verbose. git log --stat --oneline shows stats, not graph.

3. Final Answer:

   git log --oneline --graph --all -> Option D

4. Quick Check:

   Use --graph, --oneline, and --all for full branch view [OK]

Hint: Add --all to see all branches graphically [OK]

Common Mistakes:

• Omitting --all to see all branches
• Using --patch which shows code diffs, not graph
• Confusing --decorate with graph visualization