Question

A platform team adds a content exclusion rule so that files under the `config/secrets/` directory are excluded from Copilot. A developer who normally works across the whole repository reports that Copilot completions have stopped appearing entirely, even in unrelated application source files. What is the MOST likely explanation for this behavior?

Accepted Answer

The content exclusion glob pattern was written too broadly (e.g., matching the repository root), so it is unintentionally excluding far more than the intended secrets directory.

Answer

Content exclusions always disable Copilot for the entire repository once any path is excluded, so this is expected behavior.

Answer

The public-code matching filter was enabled at the same time, which suppresses all completions until the filter finishes scanning.

Answer

Content exclusions retroactively remove previously accepted suggestions, temporarily disabling new completions during the cleanup.