You should disable autocrlf
– It is not causing this “situation”, but it does collide with the gitattributes setting and adds no benefits.
You don’t have any problem with EOL conversion in your repo. The message you quoted is telling you, that if you check out this file again (with these settings), you will have CRLF in your working directory. But for now it will stay at LF.
If you want to know what line endings stuff has in your repo, run this:
git show commit:path/to/file | file -k -
If you want to get rid of that message, set your editor to save files with CRLF. Or better: If all your tools support LF endings, set this repo to use LF on checkout (if you accidentally save a file with CRLF, it will still be normalized):
git config core.eol lf
Note: this will probably only work if you set core.autocrlf
to false