SourceTree is consistently incorrect with regard to my working copy changes.
Cygwin will correctly show: "nothing to commit (working directory clean)"
But SourceTree will show seemingly random files (sometimes they are my last commited files) as modified, with mode 100755 -> 100644.
Is sourcetree attempting to change the modes of these files itself? Why? Stop it.
How do I get sourcetree to not be annoying?
-The guy who reverted back to CLI, despite sourcetree's pretty git commit history graphics, because it does too many magics that break stuff.
From my experience, Git doesn't pay attention to file permissions on the working copy. You have to explicitly modify permissions on the index, which is annoying if you have shell scripts in version control that need the executable bit set.
It's possible that SourceTree has a "feature" to detect permissions changes on the working copy and make the index changes for you as though they are a standard commit.
100755 -> 100644 implies that the executable bit has been un-set. This seems possible to be the behavior of your editor, combined with the fact that Git CLI ignores that particular type of change.
Of course, I use SourceTree on windows, so my file permissions system is not translatable to *nix permission bits, so I can't have this problem. It could be SourceTree, I suppose.
It appears that git actually recognizes these changes by default(core.fileMode=true) - https://www.kernel.org/pub/software/scm/git/docs/v188.8.131.52/git-config.html
However, the documentation states that cloning or init-ing a repo can cause it to set core.fileMode to false.. but not exactly under what circumstances it makes this change.
I'll have to double check and see what my git config looks like for that project tomorrow..
SourceTree still shows me files with that message, those files have not been changed.
For example: My LESS files are compiled to CSS, even if they are just recompiled, sourceTree still shows them to me.
We need an option to hide those files if no changes have been detected.
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event