nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

possible bug in explorer context menu.

Cameron Davidson

I am not sure where the source of the bug is, but I will set out the details. It seems quite reproducible for me.

OS: Windows 11 Pro x64 25H2.

Sourcetree V3.4.31 (also first observed on 3.4.30)

Apple iCloud Drive for Windows installed from MS Store (version - hard to tell, last updated 2026-06-19), logged in with a normal Apple account.

Open the ICloud App from the system tray (I have only Photos, Drive and Passwords enabled); under Drive, click on "Open in File Explorer"

Expected result: Opens file explorer at the virtual drive, which in my case is actually on a RAID drive G:\path-to\iCloud\drive\iCloudDrive.

When Sourcetree option "Enable 'open in sourcetree' context menu in Explorer" off then the expected result is seen.

When that option is on, then the Sourcetree program is started, and opens up at my most recent repo. There is no file explorer eventually presented.

If I open file explorer first, and use the "iCloud Drive" shortcut under "Desktop" in the folder list then it works as expected, no matter what the Sourcetree settings are. Since this more typical method of operation does not have the problem then I consider it a low priority bug.

I also tried the same thing with Google drive, and it did not have the same problem. However the only "open with file explorer" link I could find in that user interface was for mapped drives rather than subfolders, so it is not exactly the same.

Each time the the bug happens, the Sourcetree log file gets a number of entries within 1 second:

LogHost: Initializing to normal mode
ReactiveList`1: Property change notifications are enabled and type SourceTree.Model.RepositoryRemoteProjectLink isn't INotifyPropertyChanged or IReactiveObject  (This line is repeated 16 times:)
...
Could not obtain git dir, G:\path-to\iCloud\drive\iCloudDrive is not a git repo.

The same log entries occur if I manually right click and select Sourcetree->open as repository on that or similar folder (i.e. not a genuine repo)

Accepted answers

All comments

Tomislav Tobijas

Hi @Cameron Davidson ,

I'd say this is a known limitation of how Sourcetree/Windows handles virtualized drives like iCloud.

That log entry you're seeing

Could not obtain git dir, G:\path-to\iCloud\drive\iCloudDrive is not a git repo.

actually confirms that the app is successfully receiving the command to open that path, but as it isn't a Git repo, it simply opens the most recent valid repo. I think it's somewhat related to shell commands. 👀

Also, thanks for sharing the workaround! 🙏

If you don't use right-click frequently, you could completely disable it by navigating to Tools > Options > General and unchecking this "Enable 'Open in Sourcetree'..." option.

What you could also do is open JAC and create/submit a bug there. This will most likely get devs' attention, and someone should take a look at it.

Cheers,
Tobi

Cameron Davidson

Thanks @Tomislav Tobijas ,

I was under the impression that only Atlassian staff could create bug reports on Jira. It was certainly complaining about my lacking permission even just trying to search current bug reports.

I realise that Sourecetree was behaving as expected when logging that the target folder was not a repo. However, I was not asking it to open as a repo. It should not have been run at all.

I have various other 3rd party programs that add context menu "open this app here" type of commands and none of the others behave like this. So it looks to me like Sourcetree has hooked itself into the system in a way that is not correct.

Cameron.

Tomislav Tobijas

@Cameron Davidson got it. Thanks for explaining.

Yeah... it might be that Sourcetree is having some issues here. To get back to my recommendations here, raising a ticket/bug might be the best way to get attention from the devs.
You'll just have to log in with this (or any other Atlassian account) to that portal, and you'll be able to create a new ticket. Note that this works only for specific on-prem apps (such as Sourcetree), and it won't work for cloud apps and products.

Tinker Fadoua

@Cameron Davidson welcome to the community!

@Tomislav Tobijas we may request some support here since Atlassian Staff is active on the community.

Cameron Davidson

Hi,

I was anticipating logging a bug report, but am away travelling for a week or so with poor internet and no access to my desktop.

I should be able to do it mid-August

Cameron.

Tinker Fadoua

@Cameron Davidson

Any luck?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

sourcetree