“did you want benchable6 or committable6?”
Open
Nobody has claimed this yet.
bisectable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
When the message starts with HEAD, releases, 2015.12, etc. it is clear that somebody wanted to use committable or benchable, not bisectable.
I think bisectable can detect that and print a useful error message.
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 at the bisectable command handling, especially where inputs beginning with HEAD, releases, or version-like names are interpreted. Trace the existing error-message path and define the work as detecting likely committable or benchable requests and printing a useful alternative message.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100