1.2. How GitHub Copilot Fits the Developer Workflow
💡 First Principle: Copilot is not a single app you open; it is a layer that follows you across the places you already work — your editor, your terminal, GitHub.com, and your phone — all authenticated through one GitHub identity.
Why this matters: the GH-300 frequently frames questions around where a developer is working ("in the IDE," "from the command line," "reviewing a PR on GitHub.com") and asks which Copilot capability applies. If you know the surfaces and what each is good at, those questions answer themselves. Miss the surface, and you'll pick a feature that isn't available where the developer is standing.
The mental model: think of Copilot as one assistant with several doors into your workflow. The assistant is the same; the door determines which tools are within reach.
⚠️ Common Misconception: Some learners think you can use Copilot with "any account and an email" as long as the IDE supports it. Copilot authenticates through a GitHub identity everywhere — you need a GitHub account on an eligible plan or trial. An email alone, or an Azure subscription, does not grant access.
