ci: enable branch-aware shared CodeQL scanning #11

Merged
KofTwentyTwo merged 1 commits from fix/codeql-develop-20261029 into develop 2026-10-29 21:31:13 +00:00
KofTwentyTwo commented 2026-10-29 21:09:46 +00:00 (Migrated from github.com)

Add the reviewed immutable shared CodeQL caller. Preserve existing source languages and add Actions scanning. Local actionlint and actual source-inventory selection passed. Merge requires accepted exact-head scanner uploads and existing CI gates. Use a ci: squash commit so the published orb selects test-only CI maintenance without artifact publication.

Add the reviewed immutable shared CodeQL caller. Preserve existing source languages and add Actions scanning. Local actionlint and actual source-inventory selection passed. Merge requires accepted exact-head scanner uploads and existing CI gates. Use a ci: squash commit so the published orb selects test-only CI maintenance without artifact publication.
github-advanced-security[bot] commented 2026-10-29 21:29:45 +00:00 (Migrated from github.com)

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.

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](/QRun-IO/qbit-template-data/security/code-scanning?query=pr%3A11+is%3Aopen) once the scans have completed and the checks have passed. For more information about GitHub Code Scanning, check out [the documentation](https://docs.github.com/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning).
Sign in to join this conversation.