Skip to content

fix: handle Windows backslash paths in implicit clone target resolution#855

Merged
svarlamov merged 1 commit intomainfrom
fix/windows-implicit-clone-target-resolution
Mar 29, 2026
Merged

fix: handle Windows backslash paths in implicit clone target resolution#855
svarlamov merged 1 commit intomainfrom
fix/windows-implicit-clone-target-resolution

Conversation

@svarlamov
Copy link
Copy Markdown
Member

@svarlamov svarlamov commented Mar 29, 2026

Summary

Test plan

  • Added unit tests for Windows backslash paths in both derive_directory_from_url and default_clone_target_from_source
  • All 1296 lib tests pass locally
  • Windows CI jobs should now pass (all 3 modes: wrapper, daemon, wrapper-daemon)

🤖 Generated with Claude Code


Open with Devin

Both `derive_directory_from_url` and `default_clone_target_from_source`
only split on `/` to extract the last path component. On Windows, local
paths use `\` as separator, so the entire path (e.g.
`C:\Users\...\repo`) was returned as the "directory name" instead of
just the basename. This caused post-clone authorship notes fetch to fail
for implicit clone targets (no explicit directory argument).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

Open in Devin Review

@svarlamov svarlamov merged commit cae4ee5 into main Mar 29, 2026
21 checks passed
@svarlamov svarlamov deleted the fix/windows-implicit-clone-target-resolution branch March 29, 2026 21:44
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.

1 participant