Increase timespan to nag about r+ unlanded patches for test-only patches (on security bugs?)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
As per summary. Especially for security bugs, tests often can't land until the fix has been in release for a while, so the nags are annoying and pointless.
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 locating the reminder logic for r+ unlanded patches and how it identifies test-only patches or security bugs. Check the current nag interval and its tests, then verify that security-related test-only patches are not nagged until the intended longer period has elapsed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100