Skip to content

[feat] new workspace from existing branch #691

Closed

Description

@dnlopes

Describe the feature

It would be very handy to be able to import existing branches when adding workspaces. My use case is the following:

I work from multiple workstations (e.g., laptop when I'm on the move, and a Mac mini when I'm working from home), and sometimes I need to work on the same branch from both workstations. I've not been able to make this workflow work, because worktrees lifecycle are fully managed by superset, and even If I manually create worktrees based on an existing branch, superset will not find/recognize them.

Ideally, this workflow would work:

  1. from my Mac mini, start working on a new feature A by adding a new workspace: this will create a new branch and worktree
  2. finish work on the feature for the day and push changes: this would commit changes and push to remote branch
  3. from my laptop, add a new workspace based on the remote branch to continue working

Thanks.

Activity

  1. dnlopes commented on Jan 9, 2026

    @dnlopes
    Author

    I already have a branch in my fork with this change implemented. I'm just wondering whether or not you find this enhancement reasonable or not.

  2. Kitenite commented on Jan 9, 2026

    @Kitenite
    Member

    @dnlopes I think that's reasonable, I need the same feature for checking out and reviewing PR as well. For the UX, would it make sense to add that to advanced options for your workflow? Perhaps a check to create a new branch vs checking out an existing branch.

    Please feel free to open a PR and I can take a look as well :)

    Image
  3. dnlopes commented on Jan 12, 2026

    @dnlopes
    Author

    @Kitenite I had actually used the "Existing" tab, intuitively it made more sense to me, but I can see good arguments for both sides.

    I updated to use the "New" tab, something like this:

    Default state, same behavior:
    Image

    Picker disabled (branch name input becomes greyed out):
    Image

    Existing branch selected (input updated with branch name but still greyed out):
    Image

    Let me know what you think, and I can prepare a PR.

    Thanks.

  4. Kitenite commented on Jan 12, 2026

    @Kitenite
    Member

    @dnlopes Looking at it now, existing does make more sense. If you could open the PR with your ideal flow, we can take a look and update it with a finalized UX. Would that work?

    @AviPeltz for visibility

  5. dnlopes commented on Jan 13, 2026

    @dnlopes
    Author

    @Kitenite I was not able to open the PR today, but the branch is ready on my local. I will open the PR tomorrow.

  6. Kitenite commented on Jan 13, 2026

    @Kitenite
    Member

    Sounds great let me know how I can help @dnlopes !

  7. Kitenite commented on Jan 20, 2026

    @Kitenite
    Member

    Any luck on this otherwise I can prioriztize this as well

  8. chasemcdo commented on Jan 22, 2026

    @chasemcdo
    Contributor

    @Kitenite Happy to pick this up if it is not in progress - got a WIP most of the way thought it is a checkbox on the new branch but can easily be moved to existing. Wasn't really sure if the intent if that tab. It reads as it would allow you to open worktrees not in SuperSet but all of the worktrees I remove from superset get deleted, so not sure when this would actually have content in the current state.

  9. dnlopes commented on Jan 22, 2026

    @dnlopes
    Author

    @Kitenite apologies for the radio silence. I know I volunteered to open the PR upstream, but a lot of stuff happened in between, and was unable to. Sorry.

    I have the PR on my fork here, but it's not yet polished to open the final one here. I will be in PTO until next Wednesday, so I won't be able to progress until I come back.

  10. Kitenite commented on Jan 22, 2026

    @Kitenite
    Member

    @dnlopes no worries just checking in since I needed to do this as well. will get this over the line!

    @chasemcdo existing should also allow you to open from other existing worktrees. I think the future of that tab is for anything reusing an existing branch, even remote.

    Do you want to pick that up otherwise I can as well

  11. chasemcdo commented on Jan 23, 2026

    @chasemcdo
    Contributor

    Done ;)

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

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions