Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bug -- Source Control: Git Side Bar -- Doesn't display correct staged filename #27488

Closed
3ygun opened this issue May 30, 2017 · 4 comments
Closed

Bug -- Source Control: Git Side Bar -- Doesn't display correct staged filename #27488

3ygun opened this issue May 30, 2017 · 4 comments
Assignees
@joaomoreno
Labels
bug Issue identified by VS Code Team member as probable bug git GIT issues verified Verification succeeded
Milestone
June 2017

Comments

@3ygun
Copy link

3ygun commented May 30, 2017

Issue

Source Control: Git side bar doesn't show the correct staged changes. Instead showing a file that doesn't exists (DME.md in the below picture instead of README.md). Clicking the file goes into a blank comparison view. Attempting to destage README.md with git rm --cached and restage with git add doesn't correct the issue.

git status VS Code
vscode-bug vscode-bug--vscode

Steps to Reproduce:

Note: I was able to reproduce on both Windows 10 with Git Bash and a Fedora 25 instance

  1. Clone https://github.com/3ygun/tutorial-react-with-ts
  2. On master revert the last commit with git reset --soft HEAD~1
  3. See current staged files git status
  4. Open the repo in VS Code code --disable-extensions .
  5. Look at the Staged Changes in the Source Control: Git Side Bar
  6. They shouldn't match the previous output of git status with DME.md instead of README.md

Info

  • VSCode Version: Code 1.12.2 (19222cd, 2017-05-10T13:20:36.315Z)
  • OS Version: Windows_NT ia32 10.0.15063
  • Extensions: Issue reproducible with all extensions disabled (Can provide the list if need be)
@joaomoreno
Copy link
Member

Great steps, thanks!

@joaomoreno joaomoreno added bug Issue identified by VS Code Team member as probable bug git GIT issues labels Jun 13, 2017
@joaomoreno joaomoreno added this to the June 2017 milestone Jun 13, 2017
@RoarkeRandall
Copy link

Sounds like this issue #28217
I recorded this to show the issue. https://youtu.be/blNVfaq9xv8

@RoarkeRandall
Copy link

Downgrading to 1.12.2 fixed the issue for me.

@3ygun
Copy link
Author

3ygun commented Jun 17, 2017 •
edited

@RoarkeRandall while down grading may have fixed the issue you had in #28217. This is not the same issue. The resolution may come from a similar change in the git client, however:

  1. As you can see I submitted this while on version VS Code 1.12.2
  2. And can repeat the issue on VS Code 1.13.0

@michelkaporin michelkaporin added the verified Verification succeeded label Jun 29, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@joaomoreno joaomoreno

Labels
bug Issue identified by VS Code Team member as probable bug git GIT issues verified Verification succeeded
Projects
None yet
Milestone
June 2017
Development

No branches or pull requests
4 participants
@joaomoreno @michelkaporin @3ygun @RoarkeRandall