Add commands

[alexr00]

No description provided.

[Copilot]

Pull request overview

This PR adds a comprehensive commands.json configuration file for GitHub issue management automation. The file defines various automated responses and actions for issue triage, including labeling, closing, and redirecting issues based on specific comment commands or label applications.

Changes:

• Adds a new .github/commands.json file with 477 lines defining automated issue management commands

Comments suppressed due to low confidence (1)

.github/commands.json:126

• The "needsPerfInfo" command is missing the "action" field. Other similar commands that add labels use "action": "updateLabels" (e.g., "needsMoreInfo" on line 118, "jsDebugLogs" on line 130). This should be added for consistency and proper functionality.

	{
		"type": "comment",
		"name": "needsPerfInfo",
		"addLabel": "info-needed",
		"comment": "Thanks for creating this issue regarding performance! Please follow this guide to help us diagnose performance issues: https://github.com/microsoft/vscode/wiki/Performance-Issues \n\nHappy Coding!"
	},

[Copilot]

The "extGo" command is missing the "reason" field while performing a close action. All other similar extension redirect commands (extPython, extJupyter, extC, extC++, extCpp, extTS, extJS, extC#, extPowershell, etc.) include "reason": "not_planned" when they close issues. This inconsistency should be fixed to ensure the command behaves consistently with other extension redirect commands.

This issue also appears in the following locations of the same file:

• line 121

Suggested change

	"action": "close",
	"action": "close",
	"reason": "not_planned",

[Copilot]

Grammatical error: "a AI" should be "an AI". The article "an" should be used before words beginning with a vowel sound.

Suggested change

"comment": "Unfortunately I think you are hitting a AI quality issue that is not actionable enough for us to track a bug. We would recommend that you try other available models and look at the [Tips and tricks for Copilot in VS Code](https://code.visualstudio.com/docs/copilot/copilot-tips-and-tricks) doc page.\n\nWe are constantly improving AI quality in every release, thank you for the feedback! If you believe this is a technical bug, we recommend you report a new issue including logs described on the [Copilot Issues](https://github.com/microsoft/vscode/wiki/Copilot-Issues) wiki page."

"comment": "Unfortunately I think you are hitting an AI quality issue that is not actionable enough for us to track a bug. We would recommend that you try other available models and look at the [Tips and tricks for Copilot in VS Code](https://code.visualstudio.com/docs/copilot/copilot-tips-and-tricks) doc page.\n\nWe are constantly improving AI quality in every release, thank you for the feedback! If you believe this is a technical bug, we recommend you report a new issue including logs described on the [Copilot Issues](https://github.com/microsoft/vscode/wiki/Copilot-Issues) wiki page."