A developer expects a content exclusion on a secrets file to also stop that file appearing in GitHub Copilot suggestions in a different repository they work in, but it has no effect there. Which fact about exclusion propagation explains why the rule does not carry across?
- AContent exclusions are scoped to where they are configured, so a rule defined for one repository does not automatically govern files in a separate repository unless it is also set there. Correct
- BContent exclusions propagate to every repository a developer has ever cloned, so the rule failed only because the second repository was cloned before the exclusion was first created.
- CContent exclusions are stored in the developer's editor profile, so the rule only follows the individual user and never applies once a teammate opens the same secrets file instead.
- DContent exclusions only suppress matching suggestions, so the rule did apply but the second repository simply produced no completion that matched the excluded secrets file pattern.
Why A is correct: Exclusions apply within the repository or organisation scope in which they are set, so a per-repository rule has no reach into a different repository that lacks its own configuration.
Why B is wrong: Exclusions do not blanket every cloned repository based on clone order, so this invents a timing rule and misses that exclusions are scoped to where they are defined.
Why C is wrong: Exclusions are configured at the repository or organisation level rather than per user profile, so framing them as a personal editor setting describes the wrong scope.
Why D is wrong: Exclusions govern what context Copilot may read rather than matching suggestion text, so describing them as suppressing matching completions misrepresents how they work.