using inquirer or similar, build up steps of generating a list of repos, running scripts on them, and creating projects & pull requests
at every step it asks for a thing to add to its list of operations. the things could be "get a list of repos from a tako instance or json file", "filter a list with ebi", "run a script on each repo from this list", "create a pull request for each of these remote branches", "create a project board containing all of these pull requests". it maintains this as a json array in a file in the workspace, which can be replayed if/when a developer pauses doing the thing and comes back to it.
this is pretty much equivalent to the process an etg developer would go through when authoring a transformation but structuring it like this makes it less boneless
using inquirer or similar, build up steps of generating a list of repos, running scripts on them, and creating projects & pull requests
at every step it asks for a thing to add to its list of operations. the things could be "get a list of repos from a tako instance or json file", "filter a list with ebi", "run a script on each repo from this list", "create a pull request for each of these remote branches", "create a project board containing all of these pull requests". it maintains this as a json array in a file in the workspace, which can be replayed if/when a developer pauses doing the thing and comes back to it.
this is pretty much equivalent to the process an etg developer would go through when authoring a transformation but structuring it like this makes it less boneless