Opening a repo making use of core.worktree leads to many issues

[Zwyx]

Version info

• OS: Ubuntu 22.04
• Build: 2074

Description

Opening a repository which has its work tree placed somewhere else than next to the repository itself, leads to many issues. See this comment for a full description of the setup.

Issues I noticed:

• Trying to edit a commit message leads to an error, as well as trying to do a rebase.
• Signatures are shown as invalid:
  
• When closing Sublime Merge and reopening it, the list of commits is empty. We have to close the repository and reopen it to have the commit list again.

It looks like this is because Sublime Merge opens the directory of the work tree, and loses track of where the repository is, if it's not next to the work tree in the usual .git folder.

[dpjohnst]

Thanks for reporting this issue - this will be resolved in the next Sublime Merge build

[Zwyx]

Great to hear! Thanks!

[dpjohnst]

Fixed in Sublime Merge 2075 (development build)

[Zwyx]

Hi @dpjohnst, I just updated Sublime Merge to build 2077. The first two issues I mentioned above are indeed fixed, that's great, thanks for that! However, the third one is not: when closing Sublime Merge and reopening it, the list of commits is empty. We have to close the repository and reopen it to have the commit list again.

If you'd like to reopen this issue, I can cross out the two first points. Or if you prefer, I can open a new issue?