Question

A backend developer notices that ever since the platform team added a content exclusion rule for the repository's `/config/legacy-secrets/` directory, Copilot completions in a nearby service file feel less accurate. The service file itself is not excluded, but it imports and calls helper functions defined in files under the excluded directory. The developer asks why the suggestions in the allowed file seem to have gotten worse. What is the most accurate explanation?

Accepted Answer

Excluded files cannot be used as context for suggestions in other files, so Copilot loses the surrounding code it would otherwise draw from, which can reduce completion quality in files that depend on the excluded code.

Answer

Content exclusions disable Copilot completions entirely in any file that imports from an excluded path until the import is removed.

Answer

The exclusion rule corrupts Copilot's local index, and the developer must delete and re-clone the repository to restore suggestion quality.

Answer

Content exclusions only affect GitHub.com search results and have no bearing on IDE completion context, so the perceived change must be unrelated.