Skip to content

Worktree creation can create a different branch than selected remote branch #4364

Closed as duplicate

Description

@Kitenite

When creating a workspace to continue work locally on an existing remote branch, selecting the remote branch and worktree flow can still create a new local branch instead of a worktree for that existing branch.

A workaround appeared to be pasting the branch name into the top-right branch field as well, but that did not work reliably. Using claude/auto-balance-logo-sizing-1UFT7 created a different branch with casing changed, which made it look like work was happening on the same branch until opening the PR and seeing it wanted a new PR because the branch was different.

This happened even when the intended branch was selected in the branch dropdown during workspace creation.

Expected behavior: creating a workspace for an existing remote branch should create a worktree for that branch, without creating a different local branch or changing the branch name casing.

Activity

  1. added a commit that references this issue on May 10, 2026
  2. hangaoke1 commented on May 27, 2026

    @hangaoke1

    +1

  3. Kitenite commented on Jul 11, 2026

    @Kitenite
    MemberAuthor

    Closing as a duplicate of #5610, the consolidated tracker for stale workspace-creation issues from the July 2026 stale-issue sweep (no activity since 2026-06-01). If this still applies on a current build, comment on #5610 and we'll reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions