Release mgmt bot should also check the activity in the phabricator revision before unassigning good-first-bug
Open
@Archaeopteryx is already working on this.
Since Feb 16, 2022.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
https://bugzilla.mozilla.org/show_bug.cgi?id=1709204#c11
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
there was no activity in the bug comment for 2 month, but there was activity in the phabricator revision, and the last comment was made only a week ago before the Release mgmt bot unassiged.
The bot should check the activity in the phabricator revision and unassign only when there was no activity in both bug comment and phabricator comment for 2 months.
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.
Assessment
This issue has not been assessed yet.