There are a growing number of contributors and issues, and sometimes issues that are picked up by contributors are left unworked on for extended periods of time. We'd like to more easily manage how long issues are left assigned without any updates. The solution? Let's implement a GitHub Actions workflow that will leave warnings and unassign issues.
Acceptance Criteria
The bot should
leave a warning message on any issues that have not had any activity in the past 2 weeks
unassign issues that have not had any activity in the past 3 weeks (excluding the 2-week warning message)
See an example of implementing a (somewhat) similar workflow here.
Testing: testing workflows can be tricky to do directly from this repository. The best way to test this would be to work on this from within your forked repo, where you can then have infinite test runs of the workflow without requiring any approvals or affecting the existing issues in the main repo.
Hamza-Mos
commented
3 weeks ago
Description
There are a growing number of contributors and issues, and sometimes issues that are picked up by contributors are left unworked on for extended periods of time. We'd like to more easily manage how long issues are left assigned without any updates. The solution? Let's implement a GitHub Actions workflow that will leave warnings and unassign issues.
Acceptance Criteria
The bot should
Additional Context
There are a few existing GitHub actions that can be useful for implementing this bot: Close Stale Issues Unassign contributor after days of inactivity
See an example of implementing a (somewhat) similar workflow here.
Testing: testing workflows can be tricky to do directly from this repository. The best way to test this would be to work on this from within your forked repo, where you can then have infinite test runs of the workflow without requiring any approvals or affecting the existing issues in the main repo.