Configure Privacy, Content Exclusions, and Safeguards Study Guide — GH-300

Configure Privacy, Content Exclusions, and Safeguards

This domain tests your ability to configure, manage, and audit GitHub Copilot at the organization and repository level — content exclusions, output ownership, public code filtering, policy management, and audit events — plus related collaborative features inside pull requests and issues. It accounts for 14% of the exam. Questions focus on policy controls, feature availability by tier, audit and metrics access, and the exact mechanics of content exclusion, PR summaries, and code review.

Copilot PR Summaries

Copilot pull request summaries auto-generate a natural-language description of changes in a PR. The feature analyzes the diff and produces a structured summary that can be inserted into the PR description field.

How It Works

• A button labeled "Copilot" (or "Generate with Copilot") appears in the PR description editor on GitHub.com.
• Clicking it generates a summary based on the diff content, file names, and commit messages.
• The summary is editable — it populates the description box but does not auto-save.
• The author (or anyone with write access) can regenerate, edit, or discard the summary.

Availability

Common Traps

• The exam may imply that PR summaries are available on Copilot Free. They are not — they require at minimum Copilot Pro.
• PR summaries are generated from the diff, not from linked issues or project metadata.
• Summaries are not automatically inserted — a human must click the button and accept.
• PR summaries respect content exclusions: files matched by exclusion rules do not contribute content to the summary.
• This feature requires the repository to be hosted on GitHub.com (not GitHub Enterprise Server unless GHES version supports it).

Worked Scenario

A team uses Copilot Business. A developer opens a PR with 40 changed files and wants Copilot to draft the description. What action do they take?

Reasoning: Open the PR, click the "Generate with Copilot" button in the description editor. The draft appears in the text field. The developer edits and submits. No admin configuration is needed — it is on by default for Copilot Business.

Copilot Code Review

Copilot code review allows a contributor to request Copilot as a reviewer on a pull request. Copilot analyzes the diff and posts inline comments with suggestions, questions, and potential bug findings.

Requesting Copilot as a Reviewer

1. Open a PR on GitHub.com.
2. In the Reviewers panel, type or select "Copilot".
3. Copilot submits a review with inline comments. It does not approve or request changes — it only provides comments.
4. The review appears as a standard GitHub review from the github-copilot[bot] actor.

Review Behavior

Availability by Tier

Common Traps

• Copilot code review does not block merge — it cannot set branch protection requirements.
• Auto-review (triggering Copilot review automatically on every PR) is an Enterprise-only org-level policy.
• The reviewing bot appears as github-copilot[bot], not as a human user — relevant in audit log questions.
• Copilot cannot access linked issues or project board context when reviewing.
• Suggestions posted by Copilot in code review can be accepted as a commit directly from the PR UI.

Worked Scenario

A company on Copilot Business wants every new PR to automatically receive a Copilot review without developers needing to manually add the reviewer. Can they do this?

Reasoning: Auto-review on PR creation is a Copilot Enterprise feature only. Copilot Business does not support automatic review triggers. The answer is no — they must upgrade to Copilot Enterprise or have developers manually request Copilot as a reviewer.