2

I recently bought a new PC and downloaded the GitHub for Windows version: 1.2.6.4 f054d9f, then:

  1. Logged-in
  2. cloned my repo to Local
  3. made sure files were downloaded locally
  4. closed GitHub
  5. overwrote 1 file locally
  6. opened GitHub
  7. reviewed the uncommitted changes (weirdly 7 files listed, only 1 changed)
  8. synced to my repo
  9. close/open GitHub
  10. search for uncommitted changes (should be none, but there is one with 6 files)
  11. out of curiosity I made the commit and Sync
  12. the commit on the website is empty 0 changed files with 0 additions and 0 deletions.
  13. I am always stuck with these uncommitted files

enter image description here

Note: in the first edit (the one of 7 files), only the actual changed file is shown in the commit changes.

Note2: the old PC is Windows XP and the new one is Windows 7 in case that matters.

I feel like I messed something up and want to fix it, any help is appreciated.

ajax333221
  • 123

3 Answers3

1

As @Oxymoron said, it's probably an end-of-line issue.

Check core.autocrlf to make sure the values are the same on both machines.

There's a good deal of debate on what the "right value" should be. The folks on this SO thread recommend false (and so do I, but I rarely write files that are used cross-platform).

Community
  • 1
jdigital
  • 911
0

I solved this after:

  1. stop tracking the repo
  2. deleting the dir C:\Users\myname\Documents\GitHub\Isepic-Chess
  3. cloned the repo again
  4. overwritting my own source files with the downloaded local files

Note: Not sure if steps 1, 2 and 3 were necessary

ajax333221
  • 123
0

It has to do with the way you're checking out with line endings. You can check out with linux line endings, or windows line endings. if these change, it shows files as edited, it could also be the char set.

Oxymoron
  • 39