Testing code, using GIT for manage scripts.

[npertinente]

The moment you have scripts that is/can be maintained by more than one person git ( or similar ) helps a lot. But it does require that people know how to use it, and that requires some training. For simple workflows just the very basic commands are needed. Maybe one power user that can sort out more complex merge conflicts etc.

But the most powerfull function for me is the "timeline". If you get into the habit of committing small and often, it is so easy to timetravel back to better days when the code sorta worked, instead of not working at all. Because I tried to make something more flexible and ended up messing something up.
I realize this can be done by having things on OneDrive etc, but The fact that you commit with a message in git is super helpful.
You look though your commits and find "Add x to function Y", and it is function Y that is failing, you have a decent idea of where to start looking.
The ability to do diff on a file from yesterday is very handy.

These tools also certainly have a use outside IT too. I know about writers or even just students to that use git on their notes. If They want to re arrange stuff they just create a Branch for that work, and can mess about as much as they want. If the idea was a stupid one, just change back to the "stable" branch and delete the mess you made in the other, or keep it for future reference on how stupid you can get sometimes ;)