It’s simple really. Like saving a computer game and then if something doesn’t work out you can go back to a previous save game.
It only really gets tricky when multiple people are continuing on the same save and you want progress from both when you load it. But you can leave that to the most senior person to figure out.
I understand the basic concept, but what with all the forked diagrams and heads and mains and I just want to try something with my one changed parameter in one config file
It makes sense for distributed teams of contributors working on many features with governance what gets into main. For small co-located teams where probably collaboration and chronology are more important, not so much, but it’s the cool thing so people try use it for that anyway.
To be honest, as someone who only very tangentially works with git – it fucking scares me.
It’s simple really. Like saving a computer game and then if something doesn’t work out you can go back to a previous save game.
It only really gets tricky when multiple people are continuing on the same save and you want progress from both when you load it. But you can leave that to the most senior person to figure out.
I understand the basic concept, but what with all the forked diagrams and heads and mains and I just want to try something with my one changed parameter in one config file
No no, I was joking that it was simple
It makes sense for distributed teams of contributors working on many features with governance what gets into main. For small co-located teams where probably collaboration and chronology are more important, not so much, but it’s the cool thing so people try use it for that anyway.
git reflog is my best friend
It can undo things that normally one would think are “undoable”
The idea of having to dig through a reflog is scary too if you don’t have a confident intuition of how the refs work in the first place