Skip go content

Sourcetree

ApplicationAtlassian

Dem still dey call am source tree, atlassian sourcetree

AtlassianProductivity

Atlassian Git and Mercurial GUI. Di process na SourceTree.exe. E fit follow Bitbucket talk. E no be GitHub Desktop.

Wetin you need know

Sourcetree na Atlassian Git GUI, no be GitHub Desktop.

SourceTree.exe na Atlassian client and e fit Bitbucket well well. GitHub Desktop na GitHubDesktop.exe. Fork na paid Git GUI. git.exe na di engine.

Wetin e be?
Atlassian Git GUI
Same tin as GitHub Desktop?
No. Different vendor
Bitbucket friendly?
Yes. Dat one na common reason to pick am
Feex tok say
If Sourcetree no fetch, I go check di Bitbucket or Git login inside dis app. I no go uninstall GitHub Desktop make I take fix Sourcetree bookmark. Different GUIs, different saved remotes.

Wetin be Sourcetree?

Sourcetree na Atlassian desktop Git client. E no be GitHub Desktop, e no be Fork, and e no be git.exe.

If you never use am before

If your remote na Bitbucket, Sourcetree na Atlassian Git GUI. Download am from sourcetreeapp.com. SourceTree.exe fit open GitHub remotes too. GitHub Desktop na GitHub GUI and e no be dis exe. You still need Git engine.

Wetin dem dey use am for?

Visual Git history

Graph and staging. GitHub Desktop get simpler GitHub-first window.

Bitbucket accounts

Atlassian login. GitHub Desktop dey sign into GitHub, no be Bitbucket as first story.

Embedded or system Git

Sourcetree fit ship or call Git. Fork and GitHub Desktop each get dia own Git setup.

Na who e dey for?

  • Teams on top Bitbucket
  • People wey want free Atlassian Git GUI
  • Anybody wey install GitHub Desktop and no fit log into Bitbucket smoothly

Current status

Sourcetree (2013) na current git gui from Atlassian. Di vendor still dey point Windows users go https://www.sourcetreeapp.com/.

How old e be?

Atlassian ship Sourcetree for 2013. E older pass GitHub CLI and e dey di same era with GitHub Desktop. Current Windows builds still dey update. 1.x Mercurial-only memory no complete. Git na di normal workflow now.

Versions

Major channels first. Exact build numbers no dey all verified here.

Sourcetree for Windows

System requirements

Values dey follow wetin di publisher release publicly. Workload still dey change di real need.

Minimum

Minimum system requirements
Operating system Current 64-bit Windows 10 or Windows 11 release, according to Atlassian
RAM The GUI modest. Large histories want more RAM

Resource profile

CPU demand
Dey follow wetin you open inside di app
RAM demand
Dey follow documents, tabs, or libraries

Installed processes

Dese executables belong to dis product when e dey installed.

Installed processes
SourceTree.exe Sourcetree window

Startup components

Sourcetree fit open di last repo again. Dat one no be Windows service wey dem name SourceTree.

File locations

Common Sourcetree locations
Typical install C:\Users\<you>\AppData\Local\SourceTree\

File formats

GIT

Common wahala dem

Embedded Git versus system Git fights

Sourcetree options dey pick which Git. GitHub Desktop get separate Git setting.

Atlassian account prompts

Some features dey ask for Atlassian login. Dat one no be GitHub.com password.

How to get unstuck

Install from sourcetreeapp.com

Atlassian dey host di installer. Sourcetree pack on top freeware site na junk.

Tools > Options > Git

See embedded versus system Git. Dat screen no be GitHub Desktop Options.

Confirm SourceTree.exe, no be GitHubDesktop.exe

Atlassian under AppData\Local\SourceTree na dis product.

Alternatives

GitHub Desktop if di remote na GitHub-first. Fork if you want paid rebase-focused GUI. git.exe if you no want GUI.

Official help and downloads

Start with di vendor. Random exe sites no be support channel.

Official contacts
Download www.sourcetreeapp.com/ Official installer or vendor page
Help confluence.atlassian.com/sourcetree Vendor support
Official site www.sourcetreeapp.com/ Start here, no be random exe host
Atlassian Support: Sourcetree support.atlassian.com/sourcetree/ Account and Git help

Related hardware

The GUI modest. Huge repos want RAM and SSD.

Technical details

Technical details

Vendor version numbers dey change. Dis article no pin down any build.

Sources and verification

Recorded source label: August 2026. Dis label no establish independent verification. How we dey do research.

Dis article make sense to you?

Yes or no dey enough. Choose reason if you want, or add short note.

Dis article make sense to you?