AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Github desktop not showing changes11/13/2023 ![]() ![]() ![]() And that drains me of energy and interest to work on working on projects that uses git. After that, i tried to upgrade my git version to 2.25 then it fixed. After change git config core.filemode false git config tocrlf true Its still not fixed for me. But my experience of git and GitHub desktop is that it is too difficult to use, and that simple things like change of case of file name gets things messed up. For MacOS users, the following helped (on both the nix box and my desktop): git config -global tocrlf false & git config -global core.filemode true. The Project navigator annotates files with changes since the last. I fully understands that it's not something you can do anything about, and I apreciate all your help. The Xcode Project navigator showing a modified file and a new file. I tried to get my branch up to date with the projects master branch and ended up with a lot of changes in my branch, specifically because of that someone else had changed case of their files, and now git thinks that I have changed those files. A simple thing like someone else changing the case of a file can make my clone messed up. I'm very close to stop participate in the developing process of the project JMRI because I feel that git and GitHub Desktop is too difficult to use. After committing my changes, when I go to Github Desktop, I can see all my previous commits but whenever I click on one of them, I see No content changes found. I am working on my repository using vscode, and I can see the diff of my changes on vscode. If I need to change the case of a file name, I could change the file name in two steps (like file.txt to fileAAA.txt to File.txt). git version: 2.29.2 Github Desktop version: 2.6.3 Description. What kind of problem could I get if I set core.ignorecase to true? I'm using Windows 8.1 with NTFS file system. ![]()
0 Comments
Read More
Leave a Reply. |