Don't needinfo the reviewer if patch author could land a reviewed patch but hasn't yet
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
bugbot is getting too noisy. One way to reduce that a bit would be to not needinfo the reviewer about reviewed patches which haven't landed but which the patch author could land. Maybe needinfo reviewer only if the patch author doesn't respond in a week or two.
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
No file, test, or entry point is named. Locate the logic that needinfos reviewers for reviewed patches that have not landed, then inspect how patch-author activity is determined. Done means the reviewer is not needinfoed when the author can land the reviewed patch, while the proposed follow-up still covers an unresponsive author.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100