Skip to content

Unify token description for resolve-environment, start-proxy, and upload-sarif #154

Unify token description for resolve-environment, start-proxy, and upload-sarif

Unify token description for resolve-environment, start-proxy, and upload-sarif #154

Triggered via pull request February 24, 2025 18:51
Status Success
Total duration 2m 18s
Artifacts 4
Matrix: Upload debug artifacts after failure in analyze
Download and check debug artifacts after failure in analyze
5s
Download and check debug artifacts after failure in analyze
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
Upload debug artifacts after failure in analyze (nightly-latest)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (nightly-latest)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.5.
Upload debug artifacts after failure in analyze (nightly-latest)
This run of the CodeQL Action does not have permission to access Code Scanning 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 Action has the 'security-events: write' permission. Details: Resource not accessible by integration
Upload debug artifacts after failure in analyze (nightly-latest)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum
Upload debug artifacts after failure in analyze (default)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (default)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.5.
Upload debug artifacts after failure in analyze (default)
This run of the CodeQL Action does not have permission to access Code Scanning 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 Action has the 'security-events: write' permission. Details: Resource not accessible by integration
Upload debug artifacts after failure in analyze (default)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum
Upload debug artifacts after failure in analyze (linked)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (linked)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.5.
Upload debug artifacts after failure in analyze (linked)
This run of the CodeQL Action does not have permission to access Code Scanning 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 Action has the 'security-events: write' permission. Details: Resource not accessible by integration
Upload debug artifacts after failure in analyze (linked)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum
Upload debug artifacts after failure in analyze (stable-v2.20.3)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (stable-v2.20.3)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.5.
Upload debug artifacts after failure in analyze (stable-v2.20.3)
This run of the CodeQL Action does not have permission to access Code Scanning 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 Action has the 'security-events: write' permission. Details: Resource not accessible by integration
Upload debug artifacts after failure in analyze (stable-v2.20.3)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum

Artifacts

Produced during runtime
Name Size Digest
my-debug-artifacts-default Expired
19.7 MB
sha256:d42731b9342b0dbe32ed0f8ea4d419bf6303d01b6c3da96db2a82b375d39ab37
my-debug-artifacts-linked Expired
19.7 MB
sha256:a88ebad9c0166dd9e48a83e20a743875282e4da9afc15ebd3dd9dee38ed8faf4
my-debug-artifacts-nightly-latest Expired
19.7 MB
sha256:589f55fcc02ce1338c5335c931ebfb9607f1c4eaa3f1311f37e422c82d19b409
my-debug-artifacts-stable-v2203 Expired
19.6 MB
sha256:4e52550558eaaccbd5767e2e314537d8b34d84a3f472dd7735a45e6caf6d074a