multi-gitter VS gitupdate

Sounds similar to multi-gitter https://github.com/lindell/multi-gitter

It's not necessarily enforcement like the compliance pipeline but I use Multi-gitter to check if our compliance.yml is an entry in the include portion of the ci yaml file. If it's not detected it raises a MR to add it. I think this workflow would work pretty well for you too.

Multi-gitter - Run scripts across Git repos.

Yesterday I posted about multi-gitter (https://github.com/lindell/multi-gitter), but I've since found mu-repo much I much prefer. Really is fantastic for managing a large number of repos you need to perform operations on. It's lightweight and simple.

If you have a lot of repositories, in for example a GitHub org, you can do this for all of them with multi-gitter.

This is very similar to a project I created around a year ago. https://github.com/lindell/multi-gitter

Multi-gitter does also have support for other source control systems, and from what I can gather, does in general have more configuration options. But I will definitely take a look at the differences and take inspiration.

I use Sublime Merge (https://www.sublimemerge.com) for all git commands. For automating commits on things like curated lists / wikis / .. I use gitupdate (https://github.com/nikitavoloboev/gitupdate)

gitupdate is a simple improvement on this idea. gitupdate . commits your files but uses the file names (but not extensions) of the changed files to create a more meaningful commit message. It's great for times when the commit message doesn't matter.