Conversation
|
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. |
There was a problem hiding this comment.
Pull request overview
Adds a GitHub Actions workflow to run CodeQL code scanning on pushes/PRs to main and on a weekly schedule, enabling automated security/static analysis for the repo.
Changes:
- Introduces a new
.github/workflows/codeql.ymlworkflow for CodeQL scanning. - Configures a language matrix for
actionsandjavascript-typescript. - Runs CodeQL init/analyze steps (with a placeholder manual build step gated on
build-mode: manual).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - language: actions | ||
| build-mode: none | ||
| - language: javascript-typescript | ||
| build-mode: none |
There was a problem hiding this comment.
The matrix.include list items appear mis-indented relative to include: and their nested keys (build-mode). This can make the workflow YAML invalid or parse differently than intended. Re-indent include entries so the - language lines are consistently nested under include: and build-mode aligns as a sibling key within each list item (using standard 2-space YAML indentation).
| - language: actions | |
| build-mode: none | |
| - language: javascript-typescript | |
| build-mode: none | |
| - language: actions | |
| build-mode: none | |
| - language: javascript-typescript | |
| build-mode: none |
| steps: | ||
| - name: Checkout repository | ||
| uses: actions/checkout@v4 | ||
|
|
There was a problem hiding this comment.
steps: is defined, but the step list entries (- name: ...) are not indented under it. As written, this makes the workflow YAML invalid and GitHub Actions will fail to load the workflow. Indent all step items and their fields so they are nested under steps:.
|
Description
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: