Should we change the CoPilot config for the repo

[gasparnagy]

@304NotModified Should we change the config? I keep seeing these messages.

The current config is:

[clrudolphi]

I am guessing its going to be necessary if we expect it to pull assets from myget.
In addition to that, I'd suggest we grant it access to the Microsoft Learn MCP (for latest detail on .net and MS standards and conventions),
and that we establish a custom instructions.md in the solution root that outlines our internal standards/conventions and expectations of automated activity (such as code reviews and bug patching).

[304NotModified]

Yes would be great if it works with myget

[gasparnagy]

Yes would be great if it works with myget

We could publish every successful CI build to myget if this helps anyone - let's make a separate discussion about that.

[gasparnagy]

OK. I Added myget.org to the allow list (so that we don't get warnings). We don't use myget right now, but later we might.

I'd suggest we grant it access to the Microsoft Learn MCP

Do you know what should I add to the "MCP configuration" JSON for that?

[clrudolphi]

Do you know what should I add to the "MCP configuration" JSON for that?

Try something along these lines:

{
  "microsoft.docs.mcp": {
    "type": "http",
    "url": "https://learn.microsoft.com/api/mcp"
  }
}

[gasparnagy]

That does not seem to be valid.

At https://github.com/MicrosoftDocs/mcp it shows

But it should have an "mcpServers" prop. (see https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/use-copilot-agents/coding-agent/extend-coding-agent-with-mcp)

{ "mcpServers": { [something comes here] } }

We should research it on another repo, I fear.