Repository navigation
Going back and forth
One of the key points of a version control system is the ability to go back and forth between versions. To get a sense of this, go to the repository and run the following command:
$ git log --oneline
e94caba Changed version number in the skeletons main and fancymain
7fd3972 Created a plainer skeleton to avoid compile errors
4e5e5dc Cleaned up VSBR a bit
4be390a Some minor rephrase
...
This gives the list of all commits so far. The second column is the short commit message that is associated with each commit. The first column is the SHA key associated with the commit. This can be used to identify the commit.
Let us say you are up to date with the commit e94caba. But suppose you want to realise that something broke in main.tex after the VSBR cleanup (4e5e5dc) so you want to go back to main.tex in that state. You can do that by doing
$ git checkout 4e5e5dc main.tex
Now the main.tex in your current directory is what it was at state 4e5e5dc. Note that it is not that your state changed. You are still on state e94caba except that this file has been modified (to one of its previous versions). So if you wish to go back to the earlier state and start making changes from that state on, a better thing to do is create a branch on that state.
$ git checkout -b inspectVSBR 4e5e5dc
This would create a new branch called inspectVSBR that is a copy of 4e5e5dc and move you to that branch. Now you are truly in that old state (this branch will not have any of the commits that came after 4e5e5dc). You can make whatever modifications you want to make, and then maybe merge with master eventually.
There are more complicated ways of cherrypicking commits too, but we shall not get into those here. If you wish, you can look up a gazillion tutorials on that.