Open lambdatom opened 3 years ago
In my opinion, I'm not sure that ingesting a diff fits in git-xargs
core since it's something we could achieve with a script that git-xargs
can run.
Do you have a specific example scenario in mind? Perhaps I could help with adding a sample script in https://github.com/gruntwork-io/git-xargs/tree/master/scripts.
Consider adding an option which will parse a commit and compile a list changes to apply on all supplied repos.
For example, a list containing file modifications, simple word substitutions, commit message, branch name, and similar information could be inferred from the commit change(s).
Motivation: This abstraction could be applied in CI/CD pipelines to automatically propagate simple, predictable changes across many repos on a regular basis.