Organization of copilot instructions in the specs repo

[raosuhas]

With the release of the repository custom instructions for github copilot, this discussions is intended to come to an agreement on how to store the files under the .github folder for copilot instructions and also path specific custom instructions under the .githu/instructions folder.

Please go through the GH feature details here to understand the various capabilities : https://docs.github.com/en/copilot/how-tos/configure-custom-instructions/add-repository-instructions

My proposal is as follows :

• .github/copilot-instructions.md should be restricted to common instructions on building \ sdk generation that apply to the entire repo. The current file does not seem to do this.

• For files under .instructions, we organize as follows :

  • Any files named with ".codereview." , must only apply to code review agents, so it must have "excludeAgent: "coding-agent""
  • Any files named with ".codeagent." , must only apply to coding agents, so it must have "excludeAgent: "code-review""
  • Any instructions for control plane specs must have ".arm." in the name , so it must have "applyTo: "/specification//resource-manager/*.json"" and will be owned by the arm team.
  • Any instructions for data plane specs must have ".data." in the name and it must have "applyTo: "/specification//data-plane/*.json""

[raosuhas]

@mikeharder @praveenkuttappan @maririos @mikekistler @markcowl

[mikekistler]

Seems reasonable to me. I have struggled to get any utility out of the instructions we currently have, so I welcome any attempted improvements.