Repository navigation
Automate identifying, labeling, and closing stale issues #26223
Description
Outlining some of our ideas:
- Inbox:
- Identify area (was: bugs / feature requests / ...)
- Label issues filed for an insiders build as
insiders. - Label issues filed for a recently released stable build as
new release. - Search for duplicate issues.
- On bugs: Ask author to add VSCode and OS versions when not provided, also label as
needs more info. - Check description is not empty, label as
needs more info.
- Maintenance:
- Close
needs more infoissues when the last comment is from our team when stale for 7 days. - Close feature requests stale for 30 days with either no assignee or no milestone and with less than 20 up-votes
- Here 'stale' should include no addition of votes, so the voting has largely finished.
- We need to check the existing issues to assess if 30 days and 20 up-votes are good values.
- Close bugs stale for 60 days with either no milestone or on the backlog
- Close
Activity
bpasero commentedon May 15, 2017
Christof Marti (@chrmarti) Daniel Imms (@Tyriar) I found this hackathon project very relevant to our problem, maybe we can use similar techniques: https://techcrunch.com/2017/05/14/building-a-smarter-hacker-news/
bpasero commentedon Jun 2, 2017
Moving to June, I think we did not tackle automated labeling and assigning.
Configure automatic labelling of issues for insiders (#26223)
chrmarti commentedon Jun 27, 2017
new releaselabel and area classifier were implemented for the June milestone.chrmarti commentedon Jul 28, 2017
Small improvements for July (stemming in the text classifier).
chrmarti commentedon Aug 1, 2017
Closing, we'll open specific issues for future improvements.