integrate run-every
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 1.1k
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
I found https://npmjs.org/run-every today, it is super simple and lets me do stuff like this in my config:
"gititude-update": "run-every 600 bash -c \\\"gititude update || true\\\""
the bash -c part is just so I can do gititude update || true which makes it always exit with 0 so that run-every won't terminate due to non-zero exit code in case gititude update exits with non-zero
would be cool to integrate run-every into monu so you can do stuff like this easily in your config without the bash hax
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by finding where monu reads its configuration and launches commands, then compare that behavior with the run-every example and its handling of non-zero exits. Done means the requested scheduling and failure-handling behavior can be configured without the bash wrapper.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, node.js
- Domain
- desktop, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100