Repository navigation
Conversation
The porcelain v1 output parsed before is line based and C-quotes paths containing special characters (`"`, `\`, tab, newline...), and renames are reported as `old -> new` text. Such paths were shown and used with their escape sequences (e.g. `quo\"te.txt`), and a path containing ` -> ` could be split wrongly. Use the NUL-separated porcelain v2 format instead: paths are never quoted and the original path of a rename/copy is a separate field. Every status combination maps to the same `ChangeState`/`ConflictReason` as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KCxH1zwDXLd9kfAAkcf6PZ
This branch has not been deployed
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.
The porcelain v1 output parsed before is line based and C-quotes paths
containing special characters (
",\, tab, newline...), and renames arereported as
old -> newtext. Such paths were shown and used with theirescape sequences (e.g.
quo\"te.txt), and a path containing->could besplit wrongly.
Use the NUL-separated porcelain v2 format instead: paths are never quoted
and the original path of a rename/copy is a separate field. Every status
combination maps to the same
ChangeState/ConflictReasonas before.🤖 Generated with Claude Code