Git Cheat Sheet

dlang10h vertex : git allows you to be on the bleeding edge, but releases are just pointers into the git history

non-developers can ignore 99%+ of the features of git. I think what they need to know is:

git clone - get a complete archive of the project, make the most recent version what you see

git fetch - update your archive, don’t change what you see

git pull - update your archive, make the most recent version what you see

git checkout - make be what you see

If you do a git pull at random times between releases, you will get code at that random point

if you do a git pull just after a release, it’s unlikely that there will be changes.

there aren’t many bad changes that make it into the code in the first place, so the biggest problem you are likely to have pulling a random version is that you happen to hit the small window between pulling an update into the Firmeware and pulling the matching update into the Ground Control software

Also note, when you download a zip at the main github page, by default, that’s the same as doing a git clone, it’s not pulling a release, it’s pulling the most recent code.