Operating system
Windows + WSL (Ubuntu 24.04)
Orca version
1.4.110
Details
Problem or use case:
A WSL Git project added through the Orca UI did not correctly discover branches/base refs in the Create Worktree UI. The same repository registered through the Orca CLI worked correctly.
Observed behavior:
- Add a WSL Git project through the UI by browsing to a path shaped like
\\wsl.localhost\<Distro>\home\<user>\projects\<repo>.
- Open Create Worktree for that project.
- Try to create from an existing local branch or a branch that was later pushed to the remote.
- The branch/base ref is not found in the UI.
- At one point duplicate project entries for the same WSL repo also appeared.
- Removing the UI-created project and registering the same repo through the CLI made branch discovery and worktree creation work.
Working CLI registration shape:
C:\Users\<user>\AppData\Local\Programs\Orca\resources\bin\orca.cmd repo add --path \\wsl.localhost\<Distro>\home\<user>\projects\<repo> --json
Expected behavior:
A WSL project added through the UI should resolve the same repository identity, Git refs, local branches, remote branches, and default base refs as the CLI registration path.
Notes:
This looks like the UI project-add path and the CLI repo-add path may normalize or bind WSL/UNC paths differently. The UI-created project is present, but Git ref discovery in the Create Worktree flow is incomplete or stale, while the CLI-created project works.
Operating system
Windows + WSL (Ubuntu 24.04)
Orca version
1.4.110
Details
Problem or use case:
A WSL Git project added through the Orca UI did not correctly discover branches/base refs in the Create Worktree UI. The same repository registered through the Orca CLI worked correctly.
Observed behavior:
\\wsl.localhost\<Distro>\home\<user>\projects\<repo>.Working CLI registration shape:
Expected behavior:
A WSL project added through the UI should resolve the same repository identity, Git refs, local branches, remote branches, and default base refs as the CLI registration path.
Notes:
This looks like the UI project-add path and the CLI repo-add path may normalize or bind WSL/UNC paths differently. The UI-created project is present, but Git ref discovery in the Create Worktree flow is incomplete or stale, while the CLI-created project works.