Wink Pings

Copilot Moves Security Alerts into the App—Take a Close Look at the Dismiss Button First

GitHub security extension enters public preview; code scanning alerts can be viewed, explained, fixed, and dismissed in the Copilot app. As convenient as it is, the Dismiss permissions, reasons, and approval flow are worth understanding first.

GitHub has added a security extension to the Copilot app, currently in public preview. It puts code scanning alerts into a canvas called Security: view open alerts in a repository by severity, click into one to see its description, severity, and affected code; you can ask Copilot to explain it or have it modify local code. There are two installation methods: run copilot plugin install github-security@awesome-copilot in the terminal, or search for github-security in the app's Customize section and install it.

First, distinguish the two actions. Fix only changes the local working copy—it does not commit, push, or open a PR. After fixing, you still need to review the diff yourself, run tests, and go through the normal commit flow. Also, a local fix does not close the alert; only after the code lands in the affected branch and code scanning runs again will it determine whether the alert is resolved. Dismiss is different: it directly updates the alert on GitHub. The docs require selecting a reason and writing a comment. If the repository has delegated alert dismissal enabled and your role requires approval, the extension submits a dismissal request; the alert remains open, and approval is still done on GitHub.

Some people in the replies are focused on the Dismiss button. One asks whether the reason entered when dismissing an alert from chat will be visible to people doing later audits. According to the docs, the reason and comment are attached to the dismissal action. Another person warns that in enterprises the real risk often lies in exception management, rather than the finding itself. Dismissals should be managed as security exceptions: with a clear owner, expiration date, evidence attachments, and the ability to report how many open exceptions are older than 90 days. This angle is closer to what auditors see than how many alerts were fixed.

Local security review is also included. Open the session's Security canvas and click Start review, or enter /security-review in the prompt. It only checks the current changes; it does not cover a full-repository security audit and cannot replace code scanning. You can run a local review even without code scanning enabled or a GitHub Code Security license. However, to view existing repository alerts, the repository must have code scanning enabled and you must have permission to access alerts. Private repositories require GitHub Code Security. It supports GitHub.com and GitHub Enterprise Cloud with data residency, but not GitHub Enterprise Server.

The extension only displays code scanning alerts; it does not include Dependabot or secret scanning. Explain, Fix, and starting a review call the model selected in the app and consume AI credits, just like ordinary prompts. Browsing alerts and dismissing alerts do not consume AI. Tool permissions follow the app's settings; when approval is required, Copilot will ask first.

Original post: https://x.com/github/status/2122058578005487774

Docs: Viewing and fixing security alerts in the GitHub Copilot app

发布时间: 2026-11-16 08:28