vscode-gitlens icon indicating copy to clipboard operation
vscode-gitlens copied to clipboard

Fixes #3090 and #2575 - Treats .git/gitdir as cwd on "empty" bare clones

Open hwangh95 opened this issue 1 year ago • 5 comments

Description

There are cases for having bare clones with multiple worktrees in the same folder to manage various versions in a workspace

Currently, however, the only supported way to do this is to have the .git/ files such as HEAD, branches/, refs/, worktrees/, etc in the same folder as your actual worktrees. This makes your workspace very cluttered and is counterproductive to the structured way of multiple worktrees

What many of us prefer is to have an "empty" bare clone with the normal bare clone files within the .git/ folder or another folder labeled .bare and use a .git file with a gitdir reference

This fix will allow for the worktrees view to function the same way it would show on a git worktree list command

Checklist

  • [x] I have followed the guidelines in the Contributing document
  • [x] My changes follow the coding style of this project
  • [x] My changes build without any errors or warnings
  • [x] My changes have been formatted and linted
  • [x] My changes include any required corresponding changes to the documentation (including CHANGELOG.md and README.md)
  • [x] My changes have been rebased and squashed to the minimal number (typically 1) of relevant commits
  • [x] My changes have a descriptive commit message with a short title, including a Fixes $XXX - or Closes #XXX - prefix to auto-close the issue that your PR addresses

hwangh95 avatar Jan 07 '24 00:01 hwangh95

@eamodio Hello, could you please have a look at this PR?

hwangh95 avatar Jan 26 '24 09:01 hwangh95

@d13 Hey sorry for the ping but could you look at this PR? Or is there someone else who can? I've been waiting for feedback for about a month now

hwangh95 avatar Feb 14 '24 09:02 hwangh95

@d13 Still waiting for feedback on this

hwangh95 avatar Mar 26 '24 12:03 hwangh95

@axosoft-ramint Sorry for the ping, but could I get you to look into this? I've been manually compiling the source every version to fix this issue...

hwangh95 avatar Jun 20 '24 08:06 hwangh95

@hwangh95 Thanks! It may be a while before I get to this, but it's on my list now.

axosoft-ramint avatar Jun 26 '24 22:06 axosoft-ramint