Skip to content

Add CodeQL workflow for code analysis#60342

Open
MrJustinB wants to merge 2 commits into
mainfrom
MrJustinB-patch-1
Open

Add CodeQL workflow for code analysis#60342
MrJustinB wants to merge 2 commits into
mainfrom
MrJustinB-patch-1

Conversation

@MrJustinB

Copy link
Copy Markdown
Member

trying to resolve Continuous SDL warning saying we do not have CodeQL setup in this repo

Contributing to the Azure SDK

Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.

For specific information about pull request etiquette and best practices, see this section.

trying to resolve Continuous SDL warning saying we do not have CodeQL setup in this repo
@MrJustinB
MrJustinB requested a review from lmazuel June 26, 2026 22:30
@MrJustinB
MrJustinB requested a review from jsquire as a code owner June 26, 2026 22:30
Copilot AI review requested due to automatic review settings June 26, 2026 22:30
@github-advanced-security

Copy link
Copy Markdown

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:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

1 similar comment
@github-advanced-security

Copy link
Copy Markdown

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:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a GitHub Actions CodeQL workflow to enable code scanning for the repository and address the Continuous SDL warning about missing CodeQL setup.

Changes:

  • Introduces a new .github/workflows/codeql.yml workflow for CodeQL “advanced” scanning.
  • Configures a language matrix to analyze Actions, C#, JavaScript/TypeScript, and Python.
  • Schedules periodic scans and runs analysis on pushes/PRs for selected branches.

Comment thread .github/workflows/codeql.yml Outdated
Comment thread .github/workflows/codeql.yml Outdated
Comment thread .github/workflows/codeql.yml Outdated
Comment thread .github/workflows/codeql.yml Outdated
Comment thread .github/workflows/codeql.yml Outdated
Comment thread .github/workflows/codeql.yml Outdated
…nal, pin actions to SHA

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@jsquire

jsquire commented Jul 7, 2026

Copy link
Copy Markdown
Member

Not sure if this is running in CI just because it's the subject of this PR or no - but there's no way that we should be doing a full scan (90+ minutes) on every PR... Probably want some EngSys eyes on this sucker too.

//cc: @raych1, @benbp

name: "CodeQL Advanced"

on:
push:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no way we should be adding this on every PR at 90+ minutes. We'd need to very specifically scope this to only the files changed in a PR.

@raych1

raych1 commented Jul 14, 2026

Copy link
Copy Markdown
Member

Not sure if this is running in CI just because it's the subject of this PR or no - but there's no way that we should be doing a full scan (90+ minutes) on every PR... Probably want some EngSys eyes on this sucker too.

//cc: @raych1, @benbp

@jsquire This is the place where codeQl is enabled in the main build job:

@MrJustinB codeQL is already enabled for 'azure-sdk-for-net' repo and we don't need this change.
However, I do see an S360 alerts about missing python code check for this repo at here. Let me create a separate PR to solve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants