fix(ci): repoint codeql-action at a SHA that exists - #60
Conversation
github/codeql-action@29b1f65 is pinned here but exists in no repository -- the GitHub API returns 422 for it. CodeQL therefore could not start: the run graph fails to build and the job reports startup_failure, so this repository has had no CodeQL scanning at all. Repointed at 4187e74d05793876e9989daffde9c3e66b4acd07, which is what the v3 tag currently resolves to (v3.37.3), verified against the API. Found while auditing the estate: the same non-existent SHA is pinned in over 100 repositories, so CodeQL is dead across nearly all of them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
|
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. CI failed: Test failure in the project configuration suite where guix.scm defines the package as 'squisher-corpus' instead of 'supernorma'.Overview1 test failure found in the CI run due to a mismatch between package definition in Failuresguix.scm Package Definition Test Failure (confidence: high)
Summary
Code Review ✅ Approved 2 resolved / 2 findingsUpdates CodeQL actions to SHA-pinned v3 and syncs estate-wide security compliance, but the guix.scm license constructor is called with the wrong arity and package metadata refers to squisher-corpus instead of supernorma. ✅ 2 resolved✅ Bug: guix.scm license constructor called with wrong arity
✅ Quality: guix.scm renamed to squisher-corpus inside supernorma repo
Tip Comment OptionsDisplay: compact → Showing less information. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |
|




github/codeql-action@29b1f65c1f735799893313399435a59f54045865is pinned here but exists in no repository — the GitHub API returns 422 for it.CodeQL therefore could not start: the run graph fails to build and the job reports
startup_failure, so this repository has had no CodeQL scanning at all.Repointed at
4187e74d05793876e9989daffde9c3e66b4acd07, which is what thev3tag currently resolves to (v3.37.3), verified against the API.Found while auditing the estate: the same non-existent SHA was pinned in 104 repositories, so CodeQL was dead across nearly all of them.