What's changed: New GH-300 Chapter 6 (privacy settings & exclusions = content exclusion/editor settings, output ownership and limits [public-code match/licensing]; safeguards & troubleshooting = enabling duplication detection/security warnings, diagnosing suggestion/exclusion issues [exclusion/policy/seat/language], safeguards are not perfect)
6.1Privacy Settings and Content Exclusions
Understand configuring content exclusions and editor settings, and the ownership and limitations of Copilot’s output (whose it is, matches with public code, licensing caveats).
Using Copilot safely in an org requires understanding what not to send to the AI (privacy) and how to treat its output (ownership/licensing). GH-300 tests configuring content exclusions, editor-side settings, and the ownership and limitations of output.
6.1.1Content exclusions and editor settings
Content exclusion keeps specific files or repositories out of Copilot’s context and suggestions (introduced in Chapter 2). It protects sensitive config files, code that policy forbids sending to AI, and third-party confidential code. Admins set exclusions at the repo/org level; excluded files get no suggestions and aren’t used as context. The editor also has settings for enabling/disabling Copilot and target languages, combined with org policy (Chapter 2) to control scope.
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.