Skip to content

v11

v11 #1104

Triggered via pull request October 29, 2025 20:42
@thkruzthkruz
synchronize #1198
develop
Status Success
Total duration 8m 10s
Artifacts

build-pipeline.yml

on: pull_request
Yaml Lint
15s
Yaml Lint
NPM Audit Report
22s
NPM Audit Report
Matrix: Lint and Unit Tests
TruffleHog Secrets Scan
1m 2s
TruffleHog Secrets Scan
CodeQL Security Scan
2m 53s
CodeQL Security Scan
Fit to window
Zoom out
Zoom in

Annotations

1 error and 16 warnings
Yaml Lint
Process completed with exit code 1.
Lint and Unit Tests (eslint): src/plugins-pro/initial-orbit/om-manager.ts#L343
Blocks are nested too deeply (5). Maximum allowed is 4
Lint and Unit Tests (eslint): src/plugins-pro/initial-orbit/om-manager.ts#L330
Blocks are nested too deeply (6). Maximum allowed is 4
Lint and Unit Tests (eslint): src/plugins-pro/initial-orbit/om-manager.ts#L327
Blocks are nested too deeply (5). Maximum allowed is 4
Lint and Unit Tests (eslint): src/keepTrackApi.ts#L103
Unexpected console statement
Lint and Unit Tests (eslint): src/engine/rendering/gl-utils.ts#L62
Unexpected console statement
Lint and Unit Tests (eslint): src/engine/input/url-manager.ts#L643
Unexpected console statement
Lint and Unit Tests (eslint): src/engine/input/url-manager.ts#L255
Unexpected console statement
CodeQL Security Scan
Cannot create diff range extension pack for diff-informed queries; reverting to performing full analysis.
CodeQL Security Scan
Cannot retrieve the full diff because there are too many (300) changed files in the pull request.
CodeQL Security Scan
Unable to validate code scanning workflow: MissingPushHook
CodeQL Security Scan
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
CodeQL Security Scan
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.23.3.
CodeQL Security Scan
This run of the CodeQL Action does not have permission to access the CodeQL Action API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the workflow has at least the 'security-events: read' permission. Details: Resource not accessible by integration - https://docs.github.com/rest