If you forget to check out the previous day, you have to manually edit .clock.json
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
If you forget to run `clock -o`, the next day you cannot run `clock -o -a` since it's no longer today. This also implies that `clock -s/-m` does not work that day.
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
Start by reproducing the missed `clock -o` scenario, then inspect the command handling for `-o`, `-a`, `-s`, and `-m` and how `.clock.json` dates are validated. Done means a user can recover the previous day's entry with the documented commands without manually editing `.clock.json.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100