Switch CodeQL to default setup, remove advanced-setup workflow - #1075
Merged
Conversation
Enabled default setup for code scanning (actions, csharp, javascript-typescript) via the code-scanning API, which is GitHub's current recommendation for repos that don't need custom build steps - it's managed entirely by GitHub (auto-updates CodeQL versions/queries, no workflow file to maintain) instead of running our own workflow. Removed the now-redundant codeql-2.yml Advanced setup workflow: default setup disables and blocks uploads from any existing advanced-setup workflow, so keeping the file around would just waste CI minutes on a run that can't publish results. Note: GitHub's newer github-codeql-config-file repository property (for custom paths-ignore/queries under default setup) is an organization-only feature and isn't available on this personal-owned repo, so we're on plain default setup without that customization for now. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
5 tasks
KevinJump
added a commit
that referenced
this pull request
Sep 8, 2026
Enabling GitHub's default setup for code scanning at the repo level (matching v17's #1075) applies across all branches, and blocks uploads from any advanced/workflow-based CodeQL run - this workflow's PR runs on v18 were failing with "CodeQL analyses from advanced configurations cannot be processed when the default setup is enabled". Default setup now covers v18 the same way it already covers v17. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.github/workflows/codeql-2.yml(the Advanced setup workflow). Enabling default setup automatically disables and blocks uploads from any existing advanced-setup workflow, so leaving the file in place would just burn CI minutes on a run that can no longer publish results.Known limitation
GitHub recently added a
github-codeql-config-filerepository property that lets default setup pick up a custom config file (forpaths-ignore, extra queries, etc.) without needing a full workflow file. That property is an organization-only feature, andKevinJump/uSyncis owned by a personal user account, so it isn't available here. We're on plain default setup with GitHub's built-in defaults for now — nopaths-ignorecustomization possible until/unless the repo moves under an org.Test plan
state: configuredfor this repo🤖 Generated with Claude Code