fantana21/report-warnings
Count warnings and report the results in different formats
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| build-logs | Paths to the build logs. Multiple paths must be separated by newlines. Each path can be a file, a directory (all files in the directory will be included), or a wildcard pattern. The filenames of the logs must follow the format: `<compiler>_<config>_build.log`. Supported compilers are `gcc`, `clang`, `msvc`, and `clang-cl` (case-insensitive). GCC compilers can have an arbitrary prefix (without underscores) to support cross-compiling toolchains like arm-none-eabi-gcc. The configuration can be any string without underscores. The compiler and config names in the report will match the filenames exactly. For example, `GcC_deBug_build.log` will result in `GcC` as the compiler and `deBug` as the configuration in the report. | yes | — |
| include-clang-tidy-warnings | Count clang-tidy warnings too | no | true |
| add-annotations | Add annotations to the build logs if warnings are found | no | true |
| add-job-summary | Show warnings report as job summary | no | true |
| add-pr-comment | Show warnings report as sticky PR comment | no | true |
| pr-comment-header | Header to distinguish multiple PR comments | no | warnings |
| upload-artifact | Upload warnings report as job artifact | no | false |
| artifact-name | Name of the warnings report artifact | no | WarningsReport |
Outputs
no outputs