Загрузка видео...
Не удалось загрузить видео
🔒 Check your repo's code scanning alerts without leaving the GitHub Copilot app. With the new GitHub security extension, you can ask Copilot to find, explain, and fix (or dismiss!) an alert. Now in public preview ⬇️
88,528 просмотров • 1 день назад •via X (Twitter)
Комментарии: 13

one less tab open, fine by me

dismiss is the button i'll be using most, no shame

dismiss is the one i'd keep an eye on. does it leave a note on why copilot dismissed an alert so someone can check it later?

Nice follow-on to Copilot Autofix going GA for CodeQL alerts in August 2024. Fixing straight from the Copilot app is the natural next step.

dismiss is the button every agent finds first

for scanning alerts

when copilot dismisses an alert, does it have to pick a dismissal reason like false positive or used in tests, and is it limited to people who could dismiss it by hand? an agent shouldnt get more rights than the person asking

“Explain” deserves equal billing with “fix.” Understanding one vulnerability can help you spot its cousins in the next code review

A huge productivity boost for developers! 🔥 Bringing security alerts directly into Copilot makes finding and fixing vulnerabilities faster and easier. 🚀

When an agent proposes a fix, I’d want the PR to link the original finding and show the result of rerunning the same scan. That gives reviewers evidence that the change removed the finding and a way to catch it if it comes back.

can teams require human approval for dismissals while still letting the agent propose fixes? "fixed" and "hidden from the alert list" should be very different green checks

if dismissing from chat still asks for a reason, whatever you type there is what the next person auditing the repo gets to read

Triage chat falls apart the moment a monorepo logs hundreds of weekly alerts and devs start rubber-stamping fixes without running downstream integration suites.












