Question

A platform team maintains internal coding conventions, an architecture decision log, and several key configuration files that new engineers repeatedly ask Copilot Chat about. Answers are inconsistent because each developer manually pastes different snippets into chat. The team lead wants a reusable, curated context that grounds Copilot's responses in these specific documents and can be shared across the whole team. Which GitHub Copilot feature best fits this need?

Accepted Answer

Create a Copilot Space that bundles the relevant repositories, files, and free-text instructions so team members can ask questions grounded in that shared, curated context

Answer

Have each engineer enable Copilot Edits and add the documents as working-set files in their own IDE session

Answer

Configure an MCP server on each developer's machine that reads the local configuration files at query time

Answer

Turn on the Copilot content exclusion policy at the organization level so the convention files are always prioritized in prompts