Whenever I perform an action in SourceTree which alters a file in my git repo (e.g. "Discard hunk"), the edited file's permissions change from 664 to 644. This is breaking my system, because other users in the files' group need write permission.
Why is this happening, and how do I stop it? Changing my umask value did not help. I'm using OSX Mountain Lion.
EDIT after a week with no answer:
After further research and system tweaks, I'm still seeing SourceTree treating my files' permissions incorrectly. Every single file it touches gets set to 644, regardless of my umask value. I even followed the official instructions from Apple on how to set your umask for applications, and that didn't work.
Using git from the command-line does respect my umask value, so this is very frustrating.
I am having the same issue. Files and folders in the /objects dir are being created with the wrong permissions. My remote is a bare repo with the following config file: [core] repositoryformatversion = 0 filemode = true bare = true sharedRepository = true This does behavior not occur when using Git from the command line. My team is getting access errors when they pull after my push with SourceTree. This is preventing me from using Sourcetree because it is interfering with the rest of the team using command line and Eclipse. I prefer Sourcetree due to the UI. Permissions from command line and Eclipse: drwxrwsr-x 2 rossi11 hadoop 96 Feb 17 16:11 3b Permissions from Sourcetree: drwxrwx--- 2 rossi11 hadoop 51 Feb 25 11:40 3d Is there a solution for this?
Hi folks, While the full post is over on our blog I'd like to share the dark theme we've got planned for 2019 here directly as well to keep the discussion going. The ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs