RFC: remove support for ranges as a commit option
Open
Nobody has claimed this yet.
decluttering
good first issue
RFC
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
I don’t think it (e.g., 1218.12..HEAD) has ever been used in the wild so it’s just an extra code path to maintain and test.
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
No files or tests are named. Start by locating the commit-option handling and its tests, then determine how range syntax is currently accepted. Done means range support is removed consistently and the relevant tests reflect the unsupported syntax.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100