Use the published qqq-orb 0.7.14 repository-policy profile for this application-free main branch. The orb validates tracked policies/configuration and rejects application source; it does not publish an application.
Use the immutable shared source scanner owned by qqq-orb. Main and develop callers are migrated as a pair before retiring default setup. Preserve all application/smoke tests and require exact-head hosted verification plus shared scanning before merge. Canonical caller validation, actionlint and diff checks passed.
Use the published qqq-orb 0.7.14 repository-policy profile for this application-free main branch. The orb validates tracked policies/configuration and rejects application source; it does not publish an application.
Use the immutable shared source scanner owned by qqq-orb. Main and develop callers are migrated as a pair before retiring default setup. Preserve all application/smoke tests and require exact-head hosted verification plus shared scanning before merge. Canonical caller validation, actionlint and diff checks passed.
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-cluster/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).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Use the published qqq-orb 0.7.14 repository-policy profile for this application-free main branch. The orb validates tracked policies/configuration and rejects application source; it does not publish an application.
Use the immutable shared source scanner owned by qqq-orb. Main and develop callers are migrated as a pair before retiring default setup. Preserve all application/smoke tests and require exact-head hosted verification plus shared scanning before merge. Canonical caller validation, actionlint and diff checks passed.
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.