Some of the most useful runs I've used it for is for refactoring of internal libraries.
Something as simple as wanting to rename a function is theoretically very simple, but if this function is used in hundreds of other repositories, it will be very tedious.
A script that upgrades the dependency + does a replace with sed or similar could be run to make this process way easier.
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.
Using microservices created frustrations when doing smaller changes over all or most of these repositories. These changes where often small and predictable. Like fixing the builder name in a travis file, adding a pull request template or just some minor renaming refactoring.
All of these where easily scriptable, but I needed a way to run it everywhere. Hence multi-gitter was born.
Something as simple as wanting to rename a function is theoretically very simple, but if this function is used in hundreds of other repositories, it will be very tedious.
A script that upgrades the dependency + does a replace with sed or similar could be run to make this process way easier.