Define what the check covers
Record whether the review runs in Copilot CLI, the app, an SDK session or code review, and whether the input is added lines, the current change set or another supported scope. Do not describe the feature as a repository-history scanner.
Enable and test the right control
GitHub documents separate enablement paths for CLI, app, SDK and code review. Test the setting in a staging repository with a synthetic credential pattern. Confirm that the review starts, the finding reaches the intended owner and the value does not leak into logs or client-facing comments.
Create the incident handoff
For a real secret, pause the affected release path and route the finding to the credential owner. Record repository, commit or pull request, file and line, detector type, rotation status, downstream systems and client communication. History scanning and secret rotation remain separate controls.
Applicability and limits
This article applies conditionally to teams using the listed Copilot surfaces and preview settings. It does not claim that a repository or customer credential is exposed.
Primary source: Secret scanning on demand for developers and agents. Technical and editorial review remain pending.