Configure CodeQL analysis workflow for JavaScript/TypeScript - #5959
Configure CodeQL analysis workflow for JavaScript/TypeScript#5959Pammy12 (Pjrich1313) wants to merge 2 commits into
Conversation
This workflow is set up to perform CodeQL analysis on the main branch for JavaScript and TypeScript, triggered by pushes and pull requests, as well as on a schedule.
|
Pammy12 (@Pjrich1313) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
1 similar comment
|
Pammy12 (@Pjrich1313) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
There was a problem hiding this comment.
Pull request overview
Adds CodeQL scanning for JavaScript and TypeScript.
Changes:
- Runs analysis on main-branch pushes, pull requests, and weekly.
- Configures CodeQL initialization and result publishing.
Suppressed comments (2)
.github/workflows/codeql.yml:68
- Pin the CodeQL init action to an immutable commit. A mutable major tag can be retargeted, allowing upstream changes to run with
security-events: write; this also differs from the SHA-pinning convention in.github/workflows/ci.yml:51and.github/workflows/file-doc-tickets.yml:26.
uses: github/codeql-action/init@v4
.github/workflows/codeql.yml:97
- Pin the analyze action to the same immutable CodeQL release SHA as the init step. Leaving this on the mutable
v4tag exposes the write-capable workflow to upstream tag movement and is inconsistent with the repository's pinned-action convention.
uses: github/codeql-action/analyze@v4
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| # your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages | ||
| steps: | ||
| - name: Checkout repository | ||
| uses: actions/checkout@v7 |
| # required to fetch internal or private CodeQL packs | ||
| packages: read | ||
|
|
||
| # only required for workflows in private repositories | ||
| actions: read |
This workflow is set up to perform CodeQL analysis on the main branch for JavaScript and TypeScript, triggered by pushes and pull requests, as well as on a schedule.
Summary
Details
How it was tested
Impacted documentation