Conversation
- Introduced a new GitHub Actions workflow for CodeQL analysis. - Configured to run on pushes and pull requests to the main branch, as well as on a scheduled basis. - Set up to analyze JavaScript and TypeScript code using CodeQL, enhancing code security and quality checks.
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
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.
Related Issue(s)
Addresses CodeQL default setup analysis failures on main branch (Java/Kotlin, Ruby, Swift)
Motivation
The GitHub default CodeQL setup auto-detects all languages in the repository and attempts to analyze them. This causes CI failures because the repo contains minimal native module files (one Kotlin file, one Swift file) with no standalone build systems, and zero Ruby code. Replacing the default setup with a custom workflow scoped to JavaScript/TypeScript resolves these failures.
Description of Changes
Added
.github/workflows/codeql.ymlwith CodeQL analysis targeting onlyjavascript-typescriptHow to Test
Vitest) and build steps pass successfully on this PR.Checklist
Notes for Reviewers
After this PR is merged, the default CodeQL setup must be disabled in the repository settings (Settings > Code security and analysis > Code scanning) so that only this custom workflow runs. Otherwise, both will trigger and the default setup will continue to fail on Java/Kotlin, Ruby, and Swift.