Question

Your organization has configured Copilot content exclusions on a repository named 'payments-core' to block Copilot from using its files as context. A developer creates a personal fork of 'payments-core' into their own GitHub account and clones that fork locally. When they open files from the forked clone in their IDE, they notice Copilot provides inline completions using content from those files. They open a support ticket claiming content exclusions are broken. What is the most accurate explanation of this behavior?

Accepted Answer

Content exclusion rules are tied to the specific repository they are configured on and do not automatically propagate to forks residing under a different owner, so the forked repository is not covered.

Answer

Content exclusions always follow the file contents regardless of repository, so this indicates a misconfiguration in the exclusion YAML that must be fixed.

Answer

Forks inherit all content exclusion settings automatically, so the developer must simply restart the IDE to force the rules to apply.

Answer

Content exclusions are enforced by scanning file hashes, so any file matching the original is blocked even in the fork.