HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
TekWizely
run
Go2019–2026
TekWizely / run

run

Task runner that helps you easily manage and invoke small scripts and wrappers

6Distinct people
23Mentions
2Explicit recommenders
500GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Task runner that helps you easily manage and invoke small scripts and wrappers

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

I highly recommend Run [0]. [0]: https://github.com/TekWizely/run

nikolay used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year23 dated mentions

Observed mentions: 2019-12-17 22:07:16 UTC to 2026-08-03 20:55:11 UTC.

02462019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC110
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC606
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC707
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

23 sources
I made a task runner inspired by make's simplicity but purpose-built for running tasks: Run: Task runner that helps you easily manage and invoke small scripts and wrappers. https://github.com/TekWizely/run Do you find yourself using tools like make to manage non-build-related scripts? Build tools are great, but they are not optimized for general script management. Run aims to be better at managing small scripts and wrappers, while incorporating a familiar make-like syntax.
In Use Task Runners for Common Coding Tasks
A tool that I created in the same category: RUN : A Task runner that helps you easily manage and invoke small scripts and wrappers * https://github.com/TekWizely/run Do you find yourself using tools like make to manage non-build-related scripts? Build tools are great, but they are not optimized for general script management. Run aims to be better at managing small scripts and wrappers, while incorporating a familiar make-like syntax. Some features: * Auto generates command list * Auto generates help for commands * Supports defining command-line arguments, which are presented in help text * Can be composed via includes * Each command can define its own shell (or even python, etc) If you're interested in task runners, I hope you'll take a look!
In Just: A Command Runner
I use github.com/TekWizely/run for this use case. It's a robust way to build one-off command-line "APIs" for managing projects and documenting processes. I deploy it in production environments along with application-specific Runfiles for devops. It makes life a lot easier when onboarding new folks, or for remembering how to do something months later. I also use make, but limit it to just building software. All of my repos have a Runfile and a Makefile.
In Just: A Command Runner
Unrelated to this topic, I invite you take a look at my project which a tool purpose-built to be a better version of what your makefile became: Run: Task runner that helps you easily manage and invoke small scripts and wrappers https://github.com/TekWizely/run Defining commands feels like make, but comes with a bunch of extras targeted at the needs of a task-runner. I hope you'll check it out!
In DevOps is broken
This looks like an interesting way to manage scripts globally. I could even see it able to manage n-sub-commands deep (vs usual "command sub-command" - maybe it already does?) by just trying to resolve each argument as a dir until you find a script to execute. If you're interested in ways to better-manage small scripts and wrappers more locally, please take a look at my project, Run: https://github.com/TekWizely/run
In sd – a cozy nest for your scripts
Greetings! Thanks a lot for taking the time to look at Bingo. 1: re: copy-paste install script: I'll definitely grind on this and see what we can do. Bingo requires my Run[1] package, which itself is written in go and can be installed via `go install github.com/TekWizely/run` -- Additionally, once you have Bingo installed, you can use IT to re-install Run and then manage your Run installation via Bingo itself ! A self-running install script for Bingo that installs a temporary version of Run, then installs Bingo, then uses Bingo to install a permanent version of Run would actually be quite clever ! 2: re: metapackages: Bingo's goal is to be a useful wrapper on top of Go's built-in, and highly useful, install feature. Go's auto compile+install features are already getting pretty complex (ie code generation, specifying tags, etc)... The
Read the rest
fact that you can download and install hugo with `--tags extended` from the command line is pretty sweet. That said, I would say any additional support (ie metapackages) might first start as a request against go install proper -- That said, it might be a nice addition to maybe fetch some kind of `go.install` file that contains basic steps for installing a complex package. If it was going to be a non-sanctioned idea, I would still want the format of the file/spec to stand on its own and be useful outside of Bingo. 3: re: shell/path setup script: PRs always appreciated ;) 4: Graci ! I am quite pleased with myself for the name - BTW: The idea for the tool came first. I then brainstormed the name ... Thanks again and please lemme know if you have any further comments/questions! If nothing else please consider opening Issues for these ideas to help me keep track of them :) -TW [1]https://github.com/TekWizely/run
In Bingo – The missing package manager for Go binaries (Homebrew for “go install”)

Showing the 15 most recent of 23 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.