Skip to main content
The GitHub Action does this for you, and also checks files that run during CI.
Two jobs that work together:
  • On pull requests, analyze any workflow file the pull request changes.
  • On a daily schedule, scan recent runs to catch workflows that ran and were then removed or force-pushed away.

Check changed workflows

This uses the pull_request trigger, so code from forks runs without access to secrets.

Scan recent runs daily

A failure here means a workflow version that is no longer in the repository did something worth investigating. Open the run URLs from the runs array while GitHub still has the logs. Each scan costs 10 units, so a daily scan uses a small part of the 100-unit daily limit.