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

Changing only the case of a file and staging it with another file causes it to not be committed and shows the old filename #41145

Closed
joshunger opened this issue Jan 4, 2018 · 2 comments
Closed

Changing only the case of a file and staging it with another file causes it to not be committed and shows the old filename #41145

joshunger opened this issue Jan 4, 2018 · 2 comments
Assignees
@joaomoreno
Labels
bug Issue identified by VS Code Team member as probable bug git GIT issues verified Verification succeeded
Milestone
January 2018

Comments

@joshunger
Copy link
Contributor

joshunger commented Jan 4, 2018 •
edited

  • VSCode Version: Code - Insiders 1.20.0-insider (f911534, 2017-12-21T16:27:29.385Z)
  • OS Version: Darwin x64 17.3.0
  • Extensions:
Extension Author (truncated) Version
vscode-docker Pet 0.0.22
sort-lines Tyr 1.4.1
vscode-eslint dba 1.4.3
gitlens eam 7.2.0
tslint eg2 1.0.24
prettier-vscode esb 1.0.1
flow-for-vscode flo 0.7.3
intellij-idea-keybindings k-- 0.2.18
debugger-for-chrome msj 4.0.0
annotator ryu 0.11.0
vscode-fileutils sle 2.7.1

Changing only the case of a file and staging it with another file causes it to not be committed and shows the old filename git

Steps to Reproduce:

  1. Create new two files called _test1.js and _test2.js.
  2. Rename _test1.js to _Test2.js
  3. Open source control panel

EXPECTING: new filename / casing appears

ACTUAL: old filename appears

  1. Select both files and stage.

EXPECTING: both files are staged.

ACTUAL: only the non renamed file is staged. You also can't delete (Discard Changes) the renamed file and it stays "stuck".

jan-04-2018 05-09-02

Reproduces without extensions: Yes/No
@vscodebot vscodebot bot added the insiders label Jan 4, 2018
@vscodebot vscodebot bot added the git GIT issues label Jan 4, 2018
@greggb
Copy link

greggb commented Jan 5, 2018

Seeing this also, was about to open an issue, but found this one in search.

  • VSCode Version: Code 1.19.1 (0759f77, 2017-12-19T09:35:14.671Z)
  • OS Version: Darwin x64 17.3.0

I'm able to stage and commit from an external terminal, but within VSCode the file still references the original name.

@joaomoreno joaomoreno added this to the December 2017/January 2018 milestone Jan 8, 2018
@joaomoreno joaomoreno added bug Issue identified by VS Code Team member as probable bug git GIT issues and removed git GIT issues insiders labels Jan 9, 2018
@joshunger
Copy link
Contributor Author

@joaomoreno thanks

@RMacfarlane RMacfarlane added the verified Verification succeeded label Feb 2, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 23, 2018
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
January 2018
Development

No branches or pull requests
4 participants
@joaomoreno @greggb @joshunger @RMacfarlane