Sublime Forum

Sublime Merge cannot open git worktree

#1

When I try to run sublime merge with the path of git worktree in the command line I get following message:

<path> doesn't look like a git repository

At least this message is confusing. I think sublime merge should support opening worktree paths. After all it is easy to get main git repo path having worktree path.

Thanks

2 Likes

#2

I switched from GitKraken to Sublime Merge today and I experience the same issue: “foo.git doesn’t look like a git repository”
This repo uses the worktree system.

0 Likes

#3

Until this works I cannot use Sublime Merge. Almost all the repos I work with on a daily basis are just worktrees of a master bare respository.

1 Like

#4

Worktree support will be coming in a dev build later this week

3 Likes

#5

Thank you, I will gladly buy a license as soon as this feature is implemented. All my repos are based on worktrees too.

0 Likes

#6

Worktrees are supported in dev build 1063, at https://www.sublimemerge.com/dev. There’s no UI for managing them yet, this is just from the perspective of understanding the .git directory format worktrees use.

Please let me know if you run into any issues.

2 Likes

#7

I saw this fix pop up in the changelog in today’s update, but when I try to open my worktree, I’m still getting the *.git doesn't look like a git repository error message. Maybe I’m missing something on how to open it or switch to it?

1 Like

#8

Any timeframe on when the UI will support creating and otherwise using worktrees?

0 Likes

#9

Hi, will the worktree feature be included in the stable version channel anytime soon? As of right now, I cannot open any repo based on worktrees, which is 80% of my repositories. Thank you.

0 Likes

#10

@jbwe The stable channel (currently build 1075) does support opening worktrees.

If you have a repository it can’t open, I’d really appreciate it if you could file a bug report at https://github.com/sublimehq/sublime_merge/issues, and we’ll get it sorted.

When you file the bug report, in addition to the information requested, it’d be great if you could include the contents of the .git file in addition to the other requested data (NB., not the whole .git directory in the main repository, just the .git file in the worktree, which has a single line pointing to where the main repository lives).

0 Likes

#11

Thank you for your reply I will definitely do that :slight_smile:

0 Likes

#12

I created the bug report here: https://github.com/sublimehq/sublime_merge/issues/157
thank you

0 Likes

#13

core.worktree is now supported in Dev Build 1080.

0 Likes

#14

Many thanks, it works fine with core work tree, I will buy a licence right away :slight_smile:

0 Likes

#15

Hi All… it seems like this hasn’t been completely fixed in build 1119 (Win10)…

Since it looks like issues opened in the official issue tracker are not that important, I post it here too. :slight_smile:

Core.worktree is recognized but only “$git status” works

I really want to use and buy the full version of S.merge but this is actually holding me back a little bit…

Have a nice one guys!!
B

0 Likes