Adding a github enterprise account to source tree

[Isaac Rodriguez]

I was wondering if there is a way to add a github enterprise account to source tree. I can add an account, but the URL for the enterprise server cannot be edited.

[KieranA · Accepted solution]

Hey Isaac,

If you're looking for support in the hosted repositories section of SourceTree then GitHub Enterprise currently isn't supported. There are open issues for it though (SRCTREE-1182 and SRCTREEWIN-1034).

If you simply want to clone a GH:E repository then you can just clone as you normally would just without using hosted repositories. Any repository that's accessible to you whether publicly or over VPN or in your local network can be cloned into SourceTree.

Cheers

[Nadav Avidan]

And update on this? it's 2018...

[S Smith (James)]

Seriously...

[Manju]

This is coming to Sourcetree on both macOS and windows in the next few weeks. Please join the beta mailing list to get an early access build.

[DmitryM]

is not ready yet for release?

[John Gooch]

Bump. 99% of my work is on company Enterprise github :) 

[Manju]

This should be available in GA release in about 2 weeks time.

[DmitryM]

@John Gooch try to use workaround with token - solution

[Matt Hairston]

One more bump.  I see in September it should be available within two weeks.  Was there any update to this?

[Chang]

Still waiting 

[John Vandivier]

Bump. It's closed as duplicate but duplicate of what? I don't see a way to do this today. SRCTREE-1104 seems I cannot view.

[Jason Syu]

Any update on this?

[DmitryM]

I guess that on 3.2.6 version gh enterprise accounts are supported

[Xavier]

3.2.6.3544 still not working. user password and GAT.

This is a no go! I cannot recommend this over GitDesktop

[Christopher de Haan]

It seems as though GitHub Enterprise is still unsupported by SourceTree. Are there any plans to ever change that?

[Christopher de Haan]

Is there any plan for SourceTree to ever prioritize this functionality?

[Brian Do]

I was able to use GitHub Enterprise since early 2017 (and before that).  I was not sure what version I used, but after upgrading to Version 2.7.3 (169) recently, I can't no longer able to use it with GitHub Enterprise.  We need this, please!

[DmitryM]

Brian, try to use workaround with token - solution

[Alex Husarenko]

It seems as though GitHub Enterprise is still unsupported by SourceTree. Are there any plans to ever change that?

[DmitryM]

Like WA for SourceTree:

 it's possible to use GHE via access token.

1. Set up repository uri as https.
2. Generate new git access token for SourceTree in your GHE account
3. Enter your credentials on Tools -> Options -> Authentication tab with token instead of your actual account password
4. If you fail on step 3 then try to edit saved account with set up new password by token value

[andrecavaca]

Did not work for me

[andrecavaca]

After switching to System Git and updating it it started working!!

In case someone needs, Go to Tools -> Options -> Git, select System and Update in the Git Version section.

[Eric_Hedstrom]

In addition to the steps above I had to find the password in MacOS Keychain Access and replace it with the Personal Access Token as described here. Otherwise I would always get the SAML 403 error even though I had the Personal Access Token in the account settings in Sourcetree.

Using Sourcetree 4.0.1 with embedded git 2.23.0 on MacOS 10.15.4.

[DmitryM]

In the latest version hosting service includes 'GitHub Enterprise' but 2FA isn't supported. Could you support it, please?

[mustnecessity]

i use two cut image to anwer

http://i.imgur.com/n8DOH7y.png

http://i.imgur.com/xIdtWMN.png

[Sumit Goel]

Just wanted to check if GitHub Enterprise is still unsupported by SourceTree?

[Xavier]

No

[Vance Feldman]

create an access token, use that as Password, then setup SSH as normal

[Ryan Means]

I feel like just calling this out here that I highly doubt Atlassian want's to priorize - or even do it at all - because GitHub Enterprise is a direct competitor to their Stash product. GitHub's desktop client is not as feature rich as Atlassian's SourceTree so this is a natural way to try to help point business users to use stash over GH:E.

[KieranA]

Hey Ryan,

GitHub is also a direct competitor to Bitbucket, yet we support that :) this isn't anything to do with competition, we're happy to support GH:E accounts, but there hasn't been enough interest in it for us to prioritise it.

Furthermore, SourceTree doesn't stop you from using GH:E repositories at all, you just need to enter the clone URL, which is a one-time thing for a repository, so we don't stop you from using any host whatsoever. You can clone from wherever you want provided you've got access.

There's a number of factors that determine whether we're going to implement a feature; time, interest, awesomeness, and generally whether it's worth it. Because right now users can clone from GH:E it's not inhibiting them from using SourceTree with their GH:E repositories. This doesn't mean we don't think it's important, it just means for the moment they can perform all the actions like they normally can with other repositories, just without having a list of them in their hosted repositories list.

Hope that helps

[Joris Meys]

Hey Kieran, this certainly helps. As I need to be able to provide an easy interface at our faculty that works with our Enterprise version of Git at the university, you just confirmed SourceTree is not an option. If I have to explain that work flow to our students, PhDs and professors, I better find another option. Thank you

[Nathan Gray]

Kieran, this is about more than having GH:E repos listed in the hosted repos list.  It's about using SourceTree to directly open pull requests, making it a MUCH more valuable workflow tool.

[S Smith (James)]

Sorry Kieran but that doesn't cut it.

This is a very popular Google search and there are many forum posts asking about this. There have been many duplicate issues created on both the Windows and Mac versions of the issue boards which specifically ask for this.

Making it work -- according to GitHub's own API documentation -- would be as simple as allowing the users to edit the URL text box when adding a GitHub remote repo to SourceTree.

Atlassian employees comment on those duplicate posts saying that because the post is a duplicate one, the original will be escalated in importance. These "duplicates" have been coming in since 2012 and the one that's remained open is still marked as low priority.

Get one of your interns to change the textbox Active parameter from "false" to "true" and stop BSing your users! It's disgusting. 

As to whether this change is worth it or important to people or how much time it will take....your users have done the research for you. Changing the active status of a UI element is trivial and can be done in minutes. It's a $10 development cost. Open up a GoFundMe project if you don't wanna pay for it.

You guys put more time and effort into dodging the users' request than it would take to actually just implement it.

I could never recommend SourceTree to anyone, knowing that it's made by a company so willing to string people along like this. It has been years of the same cookie cutter responses to the easiest feature request.

[Nick Kirkes]

I 2nd this question!