Connect enterprise and self-hosted servers
GitTree connects to your company’s own servers: GitHub Enterprise Server, self-managed GitLab and Bitbucket Data Center. You name the host; GitTree talks to https:// that host only, and the token is used for that host only. Browser sign-in needs an OAuth application your administrator registered there.
Needs GitTree Pro or a running trial; Free keeps every local Git feature. Compare the plans.
On this page
Before you start
- GitTree Pro or a running trial: hosting integrations are part of Pro.
- The server’s host name; for browser sign-in, the OAuth application ID (and for Bitbucket Data Center its client secret) from your administrator.
Where to find it
- Preferences › Integrations › Connected accounts: Connect GitHub Enterprise Server…, Connect GitLab… or Connect Bitbucket Data Center….
| Action | macOS | Windows and Linux |
|---|---|---|
| Preferences | ⌘, | Ctrl+, |
Steps
Choose the product
Pick the connect button for your server’s product.
Name the host
Type it under Host, such as
git.example.com. GitTree shows that it talks tohttps://that host only.Choose how to sign in
Use Enter a Personal Access Token… with a token from that server, or fill OAuth application ID and sign in with the browser through the application your administrator registered.
Expected result
Repositories, pull requests and pipelines on your company server appear beside your other accounts.
What each product needs
| Product | Token | Browser sign-in |
|---|---|---|
| GitHub Enterprise Server | Personal access token | OAuth application registered on the server |
| GitLab (self-managed) | Personal access token | OAuth application registered on the server |
| Bitbucket Data Center | Personal HTTP access token | Incoming application link: client ID and client secret |
If something goes wrong
“Signing in with the browser needs this build’s … application, which is not configured. Use a token.”
Without an OAuth application for this server, use a personal access token from it.
Questions
Can a token for one server reach another?
No. Each token is stored for its own host and sent only there.