whenever command should default to --update-crontab
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 8.9k
- Forks
- 715
- PR merge metrics
- No merged PRs in 30d
Description
Right now it's really easy to overwrite everything else in your crontab by just running then whenever command. Since the crontab entry already has delimiters (also used by the --update-crontab option) to just update the section that belongs to whenever, one would expect this to be the default behavior.
Please change the default behavior of the command and add an optional --overwrite-crontab instead.
Contributor guide
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
Start by locating the command implementation and existing tests for --update-crontab and the crontab delimiters. Trace the current default and option parsing, then verify that the default updates only Whenever's section while --overwrite-crontab replaces the full crontab. Extend the relevant tests to cover both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100