Worktrees beyond read support

[p-bakker]

Hi,

Recently worktrees read support got added, which is a great step forwards!

My question is whether there's a list of known issues that need to be tackled to get this beyond just read support?

And I guess 'beyond read support' can be, at a high level be split into 2 parts:

• working inside worktrees, like: stashing, pulling, managing the index, diffing, committing etc
• worktree management, like: create, delete etc

Context: I'm trying to add worktree support in egit, where I at least want to be able to pull/stash/commit on existing worktrees.
The management of worktrees would be nice, but can live without that for now

Any thoughts appreciated!

@msohn @jvalkeal

[msohn]

I think logical next steps are to add support for creating/deleting worktrees and switching between worktrees in JGit.

[p-bakker]

Ok, so is it safe to deduct from your answer that 'working inside worktrees' part should now already be supported, so when I would expose linked worktrees in EGit, stash/pull/push/commit etc should work on them (from the jgit perspective)?