Skip to content
CI

feat: add --filter-status option for controlling which landing zones are listed #256

Sign in to view logs

feat: add --filter-status option for controlling which landing zones are listed

feat: add --filter-status option for controlling which landing zones are listed #256

Triggered via pull request September 6, 2024 11:07
@tediltedil
opened #239
landing-zone-filter-status
Status Failure
Total duration 1m 37s
Artifacts –

main.yml

on: pull_request
linting
1m 28s
linting
cancel-previous
2s
cancel-previous
Matrix: testing
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
linting
Process completed with exit code 2.
cancel-previous
The following actions uses node12 which is deprecated and will be forced to run on node16: khan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
cancel-previous
The following actions use a deprecated Node.js version and will be forced to run on node20: khan/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
linting
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2, marocchino/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
linting
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2, marocchino/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/