I recently looked at many task runners. I settled on my own personal task runner only because of familiarity. I would switch to either of these if I wasn't so heavily invested in my own tool.<p>[just](<a href="https://github.com/casey/just" rel="nofollow">https://github.com/casey/just</a>)
[task](<a href="https://github.com/go-task/task" rel="nofollow">https://github.com/go-task/task</a>)<p>I'm not sure what Run does that the two above don't.
HN is known for snark so I should say I'm genuinely not trying to be snarky. I don't understand why I would use this over a Makefile. The biggest difference is that "run" autogenerates nice help output?
Having gone through writing a couple of iterations of these, I went back to settling on `PATH="./scripts/:$PATH"`, which in my project root dirs (where I spend 99% of my time anyway on the shell) just works.<p>Sure, this could be augmented with per-folder environments, fancy runner syntax, but less is more for me in this regard.<p>Ninja update: Anyway, I like what OP is doing here, seems like a lot of things are done right in this. :)
reminds me of <a href="https://github.com/tj/robo" rel="nofollow">https://github.com/tj/robo</a>.<p>Great job on releasing this. I was just thinking about all the scripts in my makefile. Separation of concerns. I’ll be giving it a try.
This would be an interesting alternative to travis-ci or appveyor scripts (where you are locked in to that tech). By using this you can have scripts that run local or run on CI, and just have a one liner on travis-ci to call Run.
This is a great project, and I will be using it to both replace old scripts and make new ones.<p>Also, if you give me a week (I might be able to do it today or tomorrow tho), I'll submit a PR for an Archlinux PKGBUILD.
This looks pretty nice, and I like the idea of a universal help/getopts syntax that can work over different execution engines (python, bash, etc.)<p>I just did a new install at home, and may try reimplementing some of my utility scripts in terms of this just to see how it plays.
How does run compare with expect[1]?<p>1: <a href="http://manpages.ubuntu.com/manpages/bionic/man1/expect.1.html" rel="nofollow">http://manpages.ubuntu.com/manpages/bionic/man1/expect.1.htm...</a>
Good work.<p>I have done something similar by creating bash functions in a file then sourcing that, making them available as and when I want.<p>This looks nice though.