Git considers the file changed (completely) even though the file hasn't changed. what to do?

Question

git

Some strange glitch I got out. I just cloned the repository to my machine from GitHub, when I immediately get messages that I have uncommited changes (I haven’t even opened a single file yet)
And you look at the diff - and it shows the same thing twice (everything was deleted and also added the most)
How can I make git stop fooling around? Don’t want to make a meaningless commit that changes “an awl for soap” (but in fact - nothing)?

# Changes not staged for commit:
# (use "git add ..." to update what will be committed)
# (use "git checkout - ..." to discard changes in working directory)
#
# modified: game_upload/translations/ sourcecomms.phrases.txt

Answer 1

In general, the cause of the problems is amazing.
Removed from .gitattributes # Auto detect text files and perform LF normalization * text=auto, which was designed just to solve the problems of cross-platform line endings and git stopped considering that my file was changed ... I
suspect that such a gift came to me with one of the latest GitHub for Windows updates

Answer 2

Either CRLF or chmod

Answer 3

Maybe the problem is in CRLF?