Only accept valid input
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 33
- Forks
- 22
- Avg merge
- 23m
- Merged PRs (30d)
- 2
Description
GH Issue # accepts input like NNNNN, for example: https://github.com/python/cpython/pull/135857/commits/427cb1fbf43f61edcd06e0d6358059352e96cdd6
We do not allow empty input, so why should we allow invalid input?
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 tracing where blurb add reads and validates the GH Issue input, then reproduce the reported behavior with NNNNN. Done means invalid issue identifiers are rejected while valid, non-empty input continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100