git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Konstantin Hebenstreit <konstantin.hebenstreit@gmail.com>
To: git@vger.kernel.org
Subject: Bug Report git worktree
Date: Wed, 8 Feb 2023 17:40:30 +0100	[thread overview]
Message-ID: <8b445d23-245d-d6c4-b4a2-d6f3de9051a7@gmail.com> (raw)

Dear git developer community!

I'll just do a very simple small bug report.

I tried to use the git worktree command in vscode today.
vscode version: updated
git version 2.34.1

I created a worktree inside vscode, inside the extension gitlens by 
right clicking on another brach and selecting worktree.
This was not working immideately, so I first created a new folder 
(../new_folder) where I then linked the worktree to.
This was working fine. git worktree list showed both locations with 
their respective two branches.

Then I switched to the new_folder, using 'pushd'.

Bug 1)
In the Explorer field of vscode I did still see the files as they were 
before changing directory. Even if I reloaded it.
But in the shell of vscode I saw the files as they should be (as they 
are on the branch which is tied to the new_folder).

Bug 2) more problematic
worktree overwrote my settings.json file.
file:  .vscode/settings.json (not tracked by git)
Could be because the Extension 'cSpell' overwrote it. I was adding two 
new words to its dictionary, which is saved inside the settings json.
What I am left now is a settings.json that contains only the 
cSpell.words dict with two words in it. My original settings.json is gone...

Not that much of a problem, but inconvenient, as a cannot get it back, 
since git did not track it...

Hope this helps in some way!

Best,
Konstantin


                 reply	other threads:[~2023-02-08 16:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8b445d23-245d-d6c4-b4a2-d6f3de9051a7@gmail.com \
    --to=konstantin.hebenstreit@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).