fix: keep CLI fixture paths Windows-safe - #60
Closed
Teakowa wants to merge 1 commit into
Closed
Conversation
Teakowa
force-pushed
the
codex/windows-safe-cli-fixture
branch
from
August 26, 2026 07:55
7422fb6 to
be09f10
Compare
Contributor
Author
|
Superseded by #61, which carries the Windows-safe fixture change on the owner revision consumed by wright#228. |
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
1 participant
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
This is required by consumers that fetch the owner commit on Windows.
Verification
cargo test --locked --all-targets -qcargo fmt --all -- --checkremains blocked by pre-existing formatting differences outside this change