Skip to content

fix: reject multiple positional paths - #23

Merged
royalpinto007 merged 1 commit into
AgentPostmortem:mainfrom
Gambit-Checkmate:fix/reject-multiple-paths
Sep 11, 2026
Merged

fix: reject multiple positional paths#23
royalpinto007 merged 1 commit into
AgentPostmortem:mainfrom
Gambit-Checkmate:fix/reject-multiple-paths

Conversation

@Gambit-Checkmate

Copy link
Copy Markdown
Contributor

What does this PR do?

Closes #16. Reject a second positional path with a clear stderr diagnostic and exit code 2, before scanning or writing files. This avoids silently scanning only the last path.

Regression coverage includes separate/repeated paths, options between paths, an empty first argument, no ignore-file writes, and valid single/default paths. Updated usage docs and bumped the patch version with a changelog entry as requested by CONTRIBUTING.

Checklist

  • Tests pass (node --test: 17 passing entries, including fixture modules)
  • Updated docs / README if behavior changed
  • Added a CHANGELOG.md entry
  • Followed the existing code style

Notes

Developed with AI assistance. The regression test failed before the fix (exit 0 instead of 2), then the full suite passed on Windows with Node.js 24. No new dependencies.

@royalpinto007
royalpinto007 merged commit d58c385 into AgentPostmortem:main Sep 11, 2026
1 check 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.

Multiple positionals silently overwrite, only the last is kept

2 participants