It doesn't explain WHY. Alright so the file is in the staging area and needs to be committed to a repository, ok. What is the significance of this? Is a staging area a type of repository? What happens if I don't commit? Why have the add and commit stages at all - what value does that provide? Why not just have stuff either committed or NOT? etc.
Unfortunately it is one of those learning exercises written by someone who has forgotten what it was like to learn this stuff, so they presume the reader has tons of "obvious" information (or more importantly a mental model for how a git-like system SHOULD work).
Or maybe it was written with a particular audience in mind (i.e. people moving over from a different version control system).
It doesn't explain WHY. Alright so the file is in the staging area and needs to be committed to a repository, ok. What is the significance of this? Is a staging area a type of repository? What happens if I don't commit? Why have the add and commit stages at all - what value does that provide? Why not just have stuff either committed or NOT? etc.
Unfortunately it is one of those learning exercises written by someone who has forgotten what it was like to learn this stuff, so they presume the reader has tons of "obvious" information (or more importantly a mental model for how a git-like system SHOULD work).
Or maybe it was written with a particular audience in mind (i.e. people moving over from a different version control system).