git log --oneline and --graph - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Understanding git log --oneline output

What is the output format of the command git log --oneline?

Git

git log --oneline

A A graphical tree of commits with branch and merge lines.

B A list of commits showing only the commit hash and the commit message in a single line per commit.

C A list of files changed in the last commit.

D A detailed list of commits showing author, date, and full commit message.

💡 Hint

Think about what 'oneline' means for the commit display.

The --oneline option condenses each commit to one line showing the short commit hash and the commit message summary.

💻 Command Output

intermediate

Effect of --graph option in git log

What does the --graph option add to the output of git log?

Git

git log --graph

A It adds a text-based graphical representation of the commit history showing branches and merges.

B It outputs the commit history in JSON format.

C It filters commits to only those that changed files in the current directory.

D It shows only the commit hashes without messages.

💡 Hint

Think about how git visually shows branching.

The --graph option draws a simple ASCII graph showing the branching and merging structure of commits.

🔀 Workflow

advanced

Combining --oneline and --graph for commit history

Which command correctly shows a compact, graphical commit history with one line per commit?

A git log --oneline --patch

B git log --graph --stat

C git log --oneline --graph

D git log --graph --name-only

💡 Hint

You want both a graph and a short summary per commit.

Combining --oneline and --graph shows a simple graph with each commit on one line.

❓ Troubleshoot

advanced

Why does git log --graph output look misaligned?

You run git log --oneline --graph but the graph lines appear misaligned or broken in your terminal. What is the most likely cause?

A Your terminal font does not support the characters used for the graph lines.

B You forgot to add the <code>--decorate</code> option.

C The repository has no commits.

D You ran the command outside a git repository.

💡 Hint

Think about how the graph is drawn using special characters.

The graph uses special Unicode or ASCII characters that require a compatible terminal font to display properly.

🧠 Conceptual

expert

Understanding the difference between --oneline and --graph

Which statement best describes the difference between git log --oneline and git log --graph?

A <code>--oneline</code> shows only branch names; <code>--graph</code> shows commit messages.

B <code>--oneline</code> filters commits by author; <code>--graph</code> filters commits by date.

C <code>--oneline</code> shows a graphical tree; <code>--graph</code> shows commit hashes only.

D <code>--oneline</code> shortens commit info to one line; <code>--graph</code> adds a visual branch structure but does not shorten commit info.

💡 Hint

Consider what each option changes in the commit log output.

--oneline condenses each commit to a single line with short hash and message. --graph adds a visual ASCII graph showing branches and merges but does not shorten commit info by itself.

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