Keep CodeQL Scanning When Your Runner Changes

Check runners, query packs and completed results before a pipeline change.
Vulnerabilities, defensive security, architecture and operational security.

Check runners, query packs and completed results before a pipeline change.

Network origin, credentials and transaction authority need separate checks.

A proposed response record gives each service owner a clear question, an evidence reference and an unfinished decision. One team's sign-off should not silently close another's work.

A practical guide to installation evidence, exposure review and restore testing, with separate owners and clear incident-closure criteria.

Check your letter, verify the sender and match protective steps to the fields it identifies.

A recovery record should show who checked the evidence, what remains unresolved and when the next decision is due.

Decide what the next workflow can tolerate before changing where its data comes from.

Match protective steps to the personal field identified in your own notice.

Choose the destination, then prove the change.

Treat the first infected host as the starting point, not the end of the incident.