Question

An organization has configured content exclusions for a repository named 'payments-core' so that Copilot ignores its files inside developers' IDEs. A security lead notices that when browsing that same repository on GitHub.com and using Copilot Chat in the web interface to ask about the excluded files, the assistant still references their contents. The lead asks you to explain this behavior. What is the most accurate explanation?

Accepted Answer

Content exclusions apply to a defined set of Copilot surfaces (such as supported IDEs), and coverage across other surfaces like the GitHub.com web experience may differ, so exclusions are not guaranteed to be enforced everywhere identically.

Answer

Content exclusions only take effect after a 24-hour propagation window, so the web experience will honor them automatically once that period elapses.

Answer

The exclusion rules were misconfigured; a correctly written glob pattern always blocks the files across every Copilot surface including the web UI.

Answer

Content exclusions are enforced only on private repositories, so a public 'payments-core' repository would never be excluded anywhere.