Challenge 3: Why Command-Line Git Still Matters for a GUI-First Team — Solution Walkthrough

Why command-line knowledge is still valuable:

Per this chapter's own warning box, not every real Git operation or
flag is exposed in Android Studio's own GUI — a team relying
exclusively on the visual tools has no way to perform whatever
operation the GUI simply doesn't offer a button for. Encountering
exactly this kind of gap is what the team in this scenario has run
into: a real Git problem the GUI has no obvious path to solving.

Why troubleshooting specifically needs the underlying knowledge:

This chapter's own warning box also points out that troubleshooting a
genuine Git problem usually requires understanding what's actually
happening underneath — the GUI presents a simplified visual summary of
Git's own state, but diagnosing why something has gone wrong often
means reasoning about the actual underlying repository state (commit
history, branch pointers, the reflog) in a way the GUI doesn't fully
expose.

What this means practically for the team:

Falling back to the command line — even occasionally, even for a team
that prefers the GUI day to day — is a normal and expected part of
using Git seriously, not a sign the GUI has failed them. Command-line
fluency functions as a necessary backstop for exactly the situations
the GUI wasn't built to handle.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise applies this chapter's own warning box to a concrete
"the GUI has no obvious answer" scenario, correctly explaining why
command-line Git functions as a genuine backstop rather than a
redundant skill once a visual tool exists.