Skip to content

ci: run CodeQL on our runners except for fork pull requests #45

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ThePrismSystem merged 1 commit into from
Aug 6, 2026
Merged

ci: run CodeQL on our runners except for fork pull requests #45

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion .github/workflows/codeql.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,13 @@ concurrency:
jobs:
analyze:
name: Analyze
runs-on: ubuntu-latest
# The same trust boundary ci.yml draws: a fork pull request runs on
# GitHub's hardware, everything else on ours. `build-mode: none` reads the
# tree rather than running it, so the exposure here is smaller than the
# build jobs' — but a fork pull request still costs its author nothing, and
# the runner still sits on our LAN. On a push to main or the weekly cron
# the pull_request context is absent and this falls through to self-hosted.
runs-on: ${{ github.event.pull_request.head.repo.fork && 'ubuntu-latest' || 'self-hosted' }}
permissions:
security-events: write
actions: read
Expand Down
Loading