chore: bump fast-xml-parser from 5.8.0 to 5.9.2 in /actions/parse-ci-reports in the npm-dependencies group across 1 directory #791
__pull-request-ci.yml
on: pull_request
Matrix: ci / linter / 🛡️ CodeQL Analysis
ci
/
...
/
🧹 Lint Code Base
2m 15s
ci
/
...
/
prepare-actions-linting
5s
ci
/
...
/
📦 Prepare configuration
5s
Matrix: ci / test-action-matrix-outputs / Arrange - Set first output
Matrix: ci / test-action-matrix-outputs / Arrange - Set empty output
Matrix: ci / test-action-matrix-outputs / Arrange - Set third output
ci
/
...
/
Tests for checkout action
12s
ci
/
...
/
Checkout action on simulated issue_comment
7s
ci
/
...
/
Tests for get-github-actions-bot-user action
4s
ci
/
...
/
Tests for get-issue-number action
4s
ci
/
...
/
🛡️ CodeQL Analysis
57s
ci
/
...
/
🛡️ Dependency Review
8s
ci
/
...
/
Tests for parse-ci-reports action
11s
ci
/
...
/
Tests for repository-owner-is-organization action
6s
ci
/
...
/
Tests for slugify action
7s
ci
/
...
/
Tests for working-directory action
6s
Matrix: ci / test-action-matrix-outputs / Assert - Check outputs
ci
/
...
/
👕 Lint
0s
ci
/
...
/
🧪 Test
17s
Annotations
1 error and 5 warnings
|
ci / test-action-working-directory / Tests for working-directory action
The specified working directory is outside GITHUB_WORKSPACE: /tmp
|
|
ci / linter / 🛡️ CodeQL Analysis (actions)
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.
|
|
ci / test-action-checkout-issue-comment / Checkout action on simulated issue_comment
Repository is in detached HEAD state; this is expected when checking out refs/pull/<n>/head.
|
|
ci / test-action-matrix-outputs / Arrange - Set empty output (ubuntu-latest)
No data was uploaded to blob storage. Reported upload byte count is 0.
|
|
ci / test-action-matrix-outputs / Arrange - Set empty output (windows-latest)
No data was uploaded to blob storage. Reported upload byte count is 0.
|
|
ci / test-action-parse-ci-reports / continuous-integration / 🛡️ CodeQL Analysis
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.
|