cadamsdotcom
Cool idea and something pretty common. Thanks for sharing! Hope it comes in handy.
There’s also gnu parallel to run many commands in parallel while staying close to the shell. I prefer to generate a list of directories & review manually, rather than trusting a tool which may do far more than expected. The dry run option is a great help here.
For anything recurring, it’d be wise to automate - run the script from a scheduled execution system with auditing, logging, monitoring, and alerts (in case the job doesn’t run, or fails, has unexpected output etc.)
And for this use case, these days you could also ask an LLM for a one-line shell command that will do what’s needed. Copy-pasting a one-liner is my sweet spot for minimal easily reviewed shell.
There is one final nit, and I know it’s not your idea, and you are just following convention - but man do those single-dash-but-long-form arguments trigger my OCD. Anyone know why Golang introduced them?
gus_massa
clovis818
Thanks. I couldn't post with a link, new account.
brudgers
To post a link, the text box must be empty.
Mostly, you can submit text xor a link but not both.
gabrielsroka
That hasn't been true for a long time.
> If there is a url, text is optional.
github.com/clovis818/run-all is a command-line tool that allows you to execute commands across multiple directories based on a customizable directory pattern. It is designed for developers and sysadmins who need to run repetitive tasks in multiple project folders, offering options to exclude directories, run commands in parallel, and more.