{"thread":{"id":"53822","subject":"Possible bug: Changing branch with file locked","startedAt":"2020-07-09T11:01:28Z","lastAt":"2020-07-09T11:01:28Z","messageCount":1,"participants":["Antti Tanskanen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"401235","messageId":"CADGzKpxJ7_5htGVgHfvU-caPTm2tLxmCvuc-RoYkxaS=cPY1FA@mail.gmail.com","threadId":"53822","inReplyTo":null,"subject":"Possible bug: Changing branch with file locked","fromName":"Antti Tanskanen","fromEmail":"antanskan@gmail.com","sentAt":"2020-07-09T11:01:04Z","receivedAt":"2020-07-09T11:01:28Z","isPatch":false,"sender":{"key":"antanskan@gmail.com","avatar":null},"body":"Hi,\nI want to inform you about the fact when I changed a branch with VS\nCode open and git did not have permissions to address some files in\nthe other branch (or in current branch). I got an error message. That\nis OK, but my current branch got also polluted with files (from the\nother branch?). I needed to run “git stash -u” to get rid of those.\n\nI guess this can be reproduced if one locks a file which is in a\nbranch and changes the branch. Better functionality would be that git\nwould only show the error message, not to pollute the branch with\nfiles.\n\nYours,\nAntti Tanskanen\n"}]}