Every exercise here runs against a real, public repository: FireSDK — the actual client library you'll install and call in the last lesson of this track. Not a toy repo made for this lesson.
Before We Start
What's git, in one breath?
Git tracks the history of a folder of files (a "repo") — every save point, who made it, and what changed. clone downloads someone else's repo; status and diff ask "what's different right now"; commit saves a checkpoint; push sends your checkpoints somewhere else.
This lesson runs against the real, public FireSDK repository — same terminal as before, click in and type.
Done
A repo is a history you can always get back to.
Clone, status, diff, commit, branch — five commands cover most of a real workday. And those two refusals at the end were different kinds of "no": the first was git asking you to name where the new branch should go; the second was GitHub enforcing ownership — you can read JP's repo, but only JP can write to it. On your own repos, the first command git suggested would have just worked. The next two labs pick up exactly here — installing FireSDK for real, then calling it.