From: Hadi Safari <hadi@hadisafari.ir>
Date: Wed, 15 Aug 2018 19:55:24 GMT
Subject: "Changes not staged for commit" after cloning a repo on macOS
Message-ID: <6022fbe8-0e07-f561-5e66-eeb4bc92704d@hadisafari.ir>

Hi everyone!

I encountered a strange situation on OS X recently. I cloned a 
repository (https://github.com/kevinxucs/Sublime-Gitignore.git), went to 
folder, and saw "Changes not staged for commit" message for four 
specific files. It happened every time I repeated the procedure. I even 
was able to commit those to the repo.
At first I thought there's something wrong with repo, but I cloned it on 
Ubuntu 16.04 and everything was OK; no "Changes not staged for commit" 
message.

Does anyone have any idea?

Thank you.

Log:

```
$ git clone https://github.com/kevinxucs/Sublime-Gitignore.git
Cloning into 'Sublime-Gitignore'...
remote: Counting objects: 515, done.
remote: Total 515 (delta 0), reused 0 (delta 0), pack-reused 515
Receiving objects: 100% (515/515), 102.14 KiB | 48.00 KiB/s, done.
Resolving deltas: 100% (143/143), done.
$ cd Sublime-Gitignore/
$ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
   (use "git add <file>..." to update what will be committed)
   (use "git checkout -- <file>..." to discard changes in working directory)

     modified:   boilerplates/Nanoc.gitignore
     modified:   boilerplates/OpenCart.gitignore
     modified:   boilerplates/SASS.gitignore
     modified:   boilerplates/WordPress.gitignore

no changes added to commit (use "git add" and/or "git commit -a")
```

The rest of the log is available at 
https://github.com/kevinxucs/Sublime-Gitignore/issues/6. (I don't want 
this email to become too long.)

-- 
Hadi Safari
http://hadisafari.ir/