Skip to content

feat: warn when a scan reads zero files#31

Merged
ColumbusLabs merged 2 commits into
ColumbusLabs:mainfrom
ded-furby:codex/warn-on-zero-files
Jun 5, 2026
Merged

feat: warn when a scan reads zero files#31
ColumbusLabs merged 2 commits into
ColumbusLabs:mainfrom
ded-furby:codex/warn-on-zero-files

Conversation

@ded-furby
Copy link
Copy Markdown
Contributor

Summary

  • warn on stderr when a scan resolves zero files so clean output is not mistaken for a clean codebase
  • add CLI coverage for the zero-files warning path and the normal scan path
  • closes Warn when a scan resolves zero files #20

Scope

  • This change is focused on one issue or one small improvement.
  • I updated docs or examples if behavior changed.
  • I added or updated tests for code changes.

Validation

npm test
npm run typecheck:tests
npm run build

Notes for maintainers

  • The warning is advisory only; it does not change exit-code behavior for --fail-on.
  • The warning includes extra guidance for --changed scans because an empty diff is another likely cause.

@ColumbusLabs ColumbusLabs merged commit ffa3b70 into ColumbusLabs:main Jun 5, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Warn when a scan resolves zero files

2 participants