Track pull requests awaiting a response
- Dominant language
- JavaScript
- Stars
- 35.8k
- Forks
- 4.1k
- Avg merge
- 2d 26m
- Merged PRs (30d)
- 33
Description
A number of the issues or pull requests on our backlog are awaiting a response from the author (e.g. requires merge conflict resolution, requested changes on a review, or we have asked a question).
It would be good to follow on from #2627 and #2636 to track these issues with a label.
We could potentially use a workflow to automatically apply the label in some cases.
We should also consider whether we want to automatically close such issues after a certain time - however this requires some consideration, as in some cases we may be able to progress the issue/pull request without a response.
Contributor guide
Research direction
Read issues #2627 and #2636 first to understand the existing backlog-label approach. Define which unanswered cases should be tracked, whether automation is appropriate, and what policy should apply to closing them; the work is done when those decisions are agreed and the resulting tracking behavior is implemented.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100