The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Every time I try to make a change in my branch, SourceTree creates an index.lock file in the .git directory, then refuses to make the change because an index.lock file exists. Deleting the lock file doesn't help, as SourceTree will just create it again. Any suggestions?
I'm also seeing this VERY frequently in 2.7.6 (macOS 10.12.6). Has being occurring intermittently for quite a few versions now. Seems to be most common for me when the system is under high CPU load from other processes.
I still see this on 2.7.1 on macOS very regularly. I think it's a race condition somewhere in source tree as sometimes it causes it and sometimes it can sort itself out.
I have had success with closing sourctree and deleting .git/index.lock from the command line
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Getting this in v2.4.7.0 on Win10 time to time.
SourceTree creates and removes git.lock file repeatedly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Getting this in v2.4.7.0 on Win10.
Edit: It started working again right after I posted this so I think it's an intermittent issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here with 2.7. That really sucks! Atlassian please fix it. That would save my x-mas days.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the same issue with 2.6.3.
It is annoying to delete index.lock by hand after every activity.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just did an update to 2.6.3 and the index.lock issue is back again! It seems that Sourcetree creates the index.lock, then does the commit or whatever task you trigger, and at the end does not delete index.lock anymore. I manually have to delete index.lock every time I trigger an action. When will this be fixed?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Still a problem in v1.9.6.2, especially interactive rebase. Please vote on this issue to get someone working on it: https://jira.atlassian.com/browse/SRCTREEWIN-5639
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Sourcetree users!!! With the recent removal of Bitbucket Cloud account passwords for app passwords (please see our Bitbucket Cloud community post for details on why we made this change for se...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.