threads / bug / 53822

Possible bug: Changing branch with file locked

Subject: Possible bug: Changing branch with file locked

## tl;dr

One message between Jul 9, 2020 and Jul 9, 2020.

replies: 0people: 1as markdown or json

Antti Tanskanen· Jul 9, 2020, 11:01 UTC · lore

Hi, I want to inform you about the fact when I changed a branch with VS Code open and git did not have permissions to address some files in the other branch (or in current branch). I got an error message. That is OK, but my current branch got also polluted with files (from the other branch?). I needed to run “git stash -u” to get rid of those.

I guess this can be reproduced if one locks a file which is in a branch and changes the branch. Better functionality would be that git would only show the error message, not to pollute the branch with files.

Yours, Antti Tanskanen

← back to recent threads