A file is excluded, yet Copilot seems to know a type defined in it. How can that happen?
Why D is the answer
The IDE can indirectly provide semantic information, such as type details
GitHub lists this limitation: type information and hover definitions can still come through the IDE.
In detail
- The IDE can indirectly provide semantic information, such as type details.
- So excluded content can still have an influence.
- Do not treat exclusion as a way to protect secrets.
Use case
An illustrative scenario, not a real incident.
A file is excluded, yet Copilot uses one of its types correctly. The IDE supplied semantic information, which shows why exclusion is not a security boundary.
See it in different ways
flowchart TD A["Content exclusion"] --> B["Applies: supported chat and completions"] A --> C["Applies: code review on GitHub"] A --> D["Not supported: Edit and Agent modes"] A --> E["Not guaranteed: third-party MCP servers"]
stateDiagram-v2 [*] --> Excluded Excluded --> Respected: inline suggestions and chat Excluded --> NotSupported: Edit and Agent modes Excluded --> NotGuaranteed: third-party MCP servers Excluded --> Indirect: IDE semantic information
sequenceDiagram participant P0 as Excluded file participant P1 as IDE participant P2 as Copilot P0->>P1: Type definitions P1->>P2: Semantic information
Key point: Excluded content can still have indirect influence.
Why the other options are wrong
- A. Copilot downloaded the file from a backup kept in a separate location
- There is no such backup.
- B. The developer must have an enterprise owner role that overrides the rule
- Roles do not override the rule in this way.
- C. The exclusion has expired, because rules only last for a single day
- Rules do not expire after a day.