absaoss/Filename Inspector
Scans files to ensure naming conventions, reporting any files missing specified name patterns.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 19, 2026
- License
- Apache 2.0
Pinned Snippet
uses: absaoss/filename-inspector@355108975e656fac9faaa04209b6df3f9997c8fa # v0.1.1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| name-patterns | List of patterns that tested file name should have, separated by commas (e.g., "*UnitTest.*,*IntegrationTest.*"). | yes | — |
| paths | List of glob patterns of paths to include to control, separated by commas (e.g., "**/src/test/**/*.java,**/src/test/**/*.py"). | yes | — |
| excludes | List of patterns paths to exclude from controls, separated by commas (e.g., "src/exclude_dir/*.py,tests/exclude_file.py"). | no | "" |
| report-format | Specifies the format of the output report. Options: console, csv, and json. | no | console |
| verbose-logging | Enable verbose logging to provide detailed output during the action’s execution, aiding in troubleshooting and setup. | no | false |
| fail-on-violation | Set to true to fail the action if any convention violations are detected. Set to false to continue without failure. | no | false |
Outputs
| name | description |
|---|---|
| violation-count | Count of files that do not comply with the specified file name conventions. |
| report-path | Path to the generated report file. Not used when 'console' is selected as the report format. |