Don't nag about landing backed out patches
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
https://bugzilla.mozilla.org/show_bug.cgi?id=1546442
"There are some r+ patches which didn't land and no activity in this bug for 2 weeks."
The patches did actually land, but were backed out. There's a "Regressions" bug (which indeed also didn't have activity, but it doesn't seem the bot checked that).
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
Read the linked Bugzilla report and inspect the bot's reminder logic for the message about r+ patches that did not land. Reproduce the backed-out-patch scenario and verify that reminders are not sent when the original patches landed before being backed out, while the existing inactive-bug behavior remains unchanged.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100