chipsalliance/verible-linter
This action lints Verilog/SystemVerilog code
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Oct 23, 2024
- License
- Apache 2.0
Pinned Snippet
uses: chipsalliance/verible-linter-action@68df99cc51c953dcf727901905ab1d7b76f7338c # v2.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| config_file | Relative path to configuration file | no | — |
| extra_args | Extra arguments for verible-linter | no | — |
| paths | Optional array of paths to directories with source code to check | no | . |
| exclude_paths | Exclude these paths after finding all target files | no | — |
| extensions | Run linting on files ending with following extensions | no | "" |
| log_file | Name for a log file | no | verible-verilog-lint.log |
| github_token | GITHUB_TOKEN | — | "" |
| reviewdog_reporter | -reporter option to reviewdog | — | github-pr-review |
| suggest_fixes | Post results of using --autofix option as change suggestions, works only with github-pre-review reporter | — | true |
| fail_on_error | Fail the action when rule violations are found | — | false |
| verible_version | Use selected Verible version (defaults to latest release) | — | latest |
Outputs
no outputs