Skip to content
Pull Requests

fix: allow nesting catalogues #250

Sign in to view logs

fix: allow nesting catalogues

fix: allow nesting catalogues #250

Triggered via pull request November 11, 2024 10:24
@simskijsimskij
synchronize #141
fix/nested-catalogues
Status Success
Total duration 17m 27s
Artifacts –

pull-request.yaml

on: pull_request
PR  /  Check against ignorelist
6s
PR / Check against ignorelist
Terraform  /  Terraform lint
5s
Terraform / Terraform lint
PR  /  ...  /  Static Analysis of Libs
18s
PR / Quality Checks / Static Analysis / Static Analysis of Libs
PR  /  ...  /  Static Analysis of Charm
25s
PR / Quality Checks / Static Analysis / Static Analysis of Charm
PR  /  ...  /  Lint
11s
PR / Quality Checks / Linting / Lint
PR  /  ...  /  Unit tests
23s
PR / Quality Checks / Unit Tests / Unit tests
PR  /  ...  /  Scenario tests
9s
PR / Quality Checks / Scenario Tests / Scenario tests
PR  /  ...  /  Check the CHARMHUB_TOKEN secret
0s
PR / Quality Checks / Check the CHARMHUB_TOKEN secret
PR  /  ...  /  check
9s
PR / Quality Checks / Inclusive naming / check
Matrix: PR / Quality Checks / CodeQL analysis / Analyze
PR  /  ...  /  Integration Tests
16m 26s
PR / Quality Checks / Integration Tests / Integration Tests
PR  /  ...  /  Check libraries
37s
PR / Quality Checks / Check libraries
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
PR / Quality Checks / Scenario Tests / Scenario tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PR / Quality Checks / Linting / Lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PR / Quality Checks / Static Analysis / Static Analysis of Libs
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PR / Quality Checks / Unit Tests / Unit tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PR / Quality Checks / Static Analysis / Static Analysis of Charm
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PR / Quality Checks / CodeQL analysis / Analyze (python)
The following actions use a deprecated Node.js version and will be forced to run on node20: github/codeql-action/init@v2, github/codeql-action/autobuild@v2, github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PR / Quality Checks / CodeQL analysis / Analyze (python)
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
PR / Quality Checks / CodeQL analysis / Analyze (python)
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.