Skip to content

fix: report ignore-file write errors cleanly - #47

Merged
royalpinto007 merged 2 commits into
AgentPostmortem:mainfrom
Yurii201811:fix/write-error-reporting
Sep 23, 2026
Merged

royalpinto007 merged 2 commits into
AgentPostmortem:mainfrom
Yurii201811:fix/write-error-reporting

Conversation

@Yurii201811

Copy link
Copy Markdown
Contributor

What does this PR do?

I catch failures from ignore-file writes so the CLI prints its usual concise error and returns 2. This also avoids a misleading success report when the second target fails; earlier successful writes remain in place.

Closes #44.

Checklist

  • Tests pass (node --test)
  • Updated docs / README if behavior changed
  • Added a CHANGELOG.md entry
  • Followed the existing code style

Notes

31 tests pass with Node 20.20.0, plus the fixture CLI JSON smoke. The four new cases first reproduced uncaught EACCES on unchanged main, covering text/JSON output and first/second-target failure.

I bumped the patch version as required and removed the existing conflict markers from package-lock.json while synchronizing its version. No runtime dependencies were added.

Prepared with assistance from Codex.

@royalpinto007
royalpinto007 merged commit 827ba57 into AgentPostmortem:main Sep 23, 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.

--write on an unwritable dir throws a raw traceback

2 participants