Repository navigation
fix: avoid fabricated claims for unreadable files - #7
Open
xujiantop-crypto wants to merge 1 commit into
Open
xujiantop-crypto wants to merge 1 commit into
xujiantop-crypto wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
unlocatedunless the diff proves they are presentonlyFilefallback to identifiers in change sentencesThis intentionally leaves the separate Windows drive-path parsing issue out of scope.
Testing
npx vitest run tests/hooks/claims.test.ts tests/hooks/stop-claims.test.ts(20 passed)npm run type-checknpm run buildnpm run test:run(Windows: 1432 passed; 78 unrelated existing failures from symlink permissions, POSIX path assumptions, and daemon/bundle fixture paths)Fixes #5