My job uses perforce and they're trying to get as many teams off of it as possible... Which is good, perforce is pretty clunky. So I'm working on setting up a new gitlab repo and documenting it since I'm the only one on the team that has used git for anything before.
For a little context here. We have an application that's written in python that orchestrates file downloads, but there are a bunch of downloads, mostly webscrapes, that fall outside the scope of what that application can do currently. As a result we also have a directory called ~/scripts/production where hundreds of shell scripts that use curl & wget live. This is what I got into Gitlab today.
One of our problems is we can pull out all sorts of metrics about jobs we had to change or new connections we added but only as long as it's a normal job in the application where I can query the database tables... the scripts live outside all of this, and one of the things we were struggling with was like "OK we touch the one-offs really frequently because websites change all the time, but we really have no way to see whats new or what changed or why we changed it"
And because I do not trust the rest of the team to actually go through the motions of a git commit in the course of morning support, I'm going to write an autocommit & autopush job that runs every friday

