Skip to content

subparser: use full parser path instead of just parser name in usage() message #123

subparser: use full parser path instead of just parser name in usage() message

subparser: use full parser path instead of just parser name in usage() message #123

Triggered via pull request November 8, 2024 19:49
Status Success
Total duration 43s
Artifacts 1

tidy-analysis-stage-01.yml

on: pull_request
clang-tidy
35s
clang-tidy
Fit to window
Zoom out
Zoom in

Annotations

1 warning
clang-tidy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
clang-tidy-result
533 Bytes