Adding standard responses to the issue bot that can be triggered by team members and in some cases the community.

The first stage focuses on simple cases so we can get these deployed early in the milestone and the team can use them for the issue cleanup:

• A team member adds a label and the bot closes the issue with a standard response in response.
  • Labels: question, extension-candidate, not-reproducible, out-of-scope
  • For each label there will be a standard comment in Markdown with links to more information.
• A team member can add a comment of the form '/duplicate of Sub menus by extensions in explorer context menus,item menus #12321' and the bot will label the issue as duplicate and close it with an explanatory comment.
• Issues closed for 30 days or longer are locked by the bot.

The second stage is slightly more complex and involves the community:

• Confirmation flow
  • A team member (or for some areas the bot) labels the issue as confirmation-needed and the bot adds an explanatory comment.
  • Anyone other than the issue's creator adds a comment of the from /confirm and the bot removes the confirmation-needed label and adds the confirmed label instead.
  • The owner is assigned by the inbox tracker (or automatically) when the issue is labeled confirmed.
• Vested community members: We will restrict the power to confirm an issue and extend the power to mark duplicates to active members of the community.
  • How this can be queried needs to be explored.