What do these words mean in Git: Repository, fork, branch, clone, track?

Question

I\'m honestly not clear on the semantics here. They\'re all about copies/variants of a code+history unit, but past that I\'m not sure I could say. Is this logical structure ex

Answer 1

I'm going to answer my own question with an RTFM.

But, read this fine manual. As the author puts it:

“The conclusion I draw from this is that you can only really use Git if you understand how Git works. Merely memorizing which commands you should run at what times will work in the short run, but it’s only a matter of time before you get stuck or, worse, break something.

“Half of the existing resources on Git, unfortunately, take just that approach: they walk you through which commands to run when, and expect that you should do fine if you just mimic those commands. The other half does go through all the concepts, but from what I have seen, they explain Git in a manner that assumes you already understand how Git works.”