Drop `tests` label if new commits extend the scope outside tests
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 62
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
Example cases where tests label remained, but the PR did not finally touch tests only:
- https://github.com/python/cpython/pull/143047 (started with a failing test, then implemented the fix)
- https://github.com/python/cpython/pull/143045 (started with a failing test, then implemented the fix)
If this isn't overly complicated, let's ensure the labels are up-to-date with every new commit.
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 tracing how the bot applies and updates the tests label as commits arrive, then compare the behavior with pull requests 143047 and 143045. Done means a pull request that begins with tests and later adds implementation changes no longer retains an inaccurate tests label.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100