I tended to find that a few things were likely to go wrong and simply changing the git workflow scripts to account for those things was enough. If things went

I tended to find that a few things were likely to go wrong and simply changing the git workflow scripts to account for those things was enough. If things went wrong, people could come to me. That often resulted in me fixing their problem and fixing the script to ensure that kind of problem didn't happen again - after which people stopped coming to me because they didn't have problems. Basically it was like releasing software. >I submit this must be because people came out of the course without really understanding the tool. I submit that not everybody needs to be an expert in the tool. Non-programmers can actually help a lot with writing stuff that needs to be version controlled with code - e.g. writing test scripts, updating translations, various configurations, etc.