ci: centralize branch verification and source scanning #6

2026-10-21T17:17:50Z

KofTwentyTwo commented

2026-10-21 17:17:50 +00:00

(Migrated from github.com)

Use verified qqq-orb 0.7.15 and the immutable shared source scanner owned by qqq-orb. Main and develop callers are migrated as a pair before retiring default setup. Preserve the branch's application/policy profile, all application/smoke tests, and require exact-head hosted verification plus shared scanning before merge. Canonical caller validation, actionlint and diff checks passed.

Replace the temporary RC.7/local help snapshot dependency with published core4.1.0-RC.11 and update build instructions. Full Maven verification passed:21tests,0failures/errors/skips,coverage gates passed. Preserve main as the default branch and the develop application release policy.

Use verified qqq-orb 0.7.15 and the immutable shared source scanner owned by qqq-orb. Main and develop callers are migrated as a pair before retiring default setup. Preserve the branch's application/policy profile, all application/smoke tests, and require exact-head hosted verification plus shared scanning before merge. Canonical caller validation, actionlint and diff checks passed. Replace the temporary RC.7/local help snapshot dependency with published core4.1.0-RC.11 and update build instructions. Full Maven verification passed:21tests,0failures/errors/skips,coverage gates passed. Preserve main as the default branch and the develop application release policy.

github-advanced-security[bot] commented

2026-10-21 17:19:38 +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-help/security/code-scanning?query=pr%3A6+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.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-help#6