fix(codeql): analyse the languages this repository actually has - #42
Conversation
`codeql database finalize` was exiting 32 on every run:
CodeQL could not process any code written in JavaScript/TypeScript.
The matrix asserted javascript-typescript, which this repository does not contain.
Its languages are: ruby,rust.
This is not only a failing check. The crash uploads no SARIF, so a
`code_scanning` ruleset rule requiring CodeQL waits forever on "Code scanning
is waiting for results from CodeQL" — one fault, two symptoms. Relaxing the
rule's thresholds could not have helped, because no results arrive at all.
New matrix: actions, ruby, rust. `actions` is valid in every repository (every
repository has workflow files) and keeps this workflow producing a check and a
SARIF upload even where CodeQL can analyse nothing else — most of this estate
is written in languages CodeQL does not support.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
|
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
| - language: ruby | ||
| build-mode: none |
There was a problem hiding this comment.
💡 Edge Case: Ruby leg rests on a single Homebrew formula
The only Ruby in the repo is packaging/homebrew/cloud-sync-tuner.rb (a Homebrew Formula class). If CodeQL's Ruby extractor treats this lone packaging file as non-substantive, the ruby matrix leg can exit 32 ("could not process any code") — the exact failure this PR fixes — and, since a leg failure means no SARIF for that language, it could re-block the code_scanning ruleset. Verify the ruby analysis actually succeeds; if the formula is the only Ruby, consider dropping the ruby leg (the actions leg already guarantees a check/SARIF).
Was this helpful? React with 👍 / 👎
There was a problem hiding this comment.
Configure merge blocking · Maintainers can dismiss this review.
|
Note Automatic reviews are paused because your trial's included automatic processing has been used for this period. Upgrade now, or comment "Gitar review" to run a review anytime. Code Review 👍 Approved with suggestions 0 resolved / 1 findingsUpdates the CodeQL workflow matrix from JavaScript/TypeScript to Ruby and Rust to resolve pipeline failures and missing SARIF uploads. Consider whether analyzing Ruby is necessary given it only consists of a single Homebrew formula.
💡 Edge Case: Ruby leg rests on a single Homebrew formula📄 .github/workflows/codeql.yml:35-36 The only Ruby in the repo is packaging/homebrew/cloud-sync-tuner.rb (a Homebrew Formula class). If CodeQL's Ruby extractor treats this lone packaging file as non-substantive, the 🤖 Prompt for agentsOptionsDisplay: compact → Showing less information. Comment with these commands to change the behavior for this request:
Important Your trial ends in 4 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more. Was this helpful? React with 👍 / 👎 | Gitar |
|
|



codeql database finalizewas exiting 32 on every run:The matrix asserted
javascript-typescript; this repository's languages areruby,rust. Onecodeql.ymlwas copied estate-wide with a hard-coded JS matrix — 82 repositories carry it, and 17 of the 18 sampled have no JavaScript at all (Julia, Rust, Zig, Agda, Ada, Haskell, Elixir).This is not only a failing check. The crash uploads no SARIF, so a
code_scanningruleset rule requiring CodeQL waits forever on "Code scanning is waiting for results from CodeQL". One fault, two symptoms — and relaxing the rule's thresholds could not have helped, because no results arrive at all.actionsis kept (or added): it is valid in every repository, since every repository has workflow files, and it keeps this workflow producing a check and a SARIF upload even where CodeQL can analyse nothing else.🤖 Generated with Claude Code