Connect GitLab
GitTree connects to gitlab.com or to a self-managed GitLab host you name. Sign in with the browser through an OAuth application (for gitlab.com GitTree’s own is used), or use a personal access token from that host. The token is used for that host only.
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.
- For a self-managed host: its address, and an OAuth application ID from your administrator if you want to sign in with the browser.
Where to find it
- Preferences › Integrations › Connected accounts: Connect GitLab….
| Action | macOS | Windows and Linux |
|---|---|---|
| Preferences | ⌘, | Ctrl+, |
Steps
Choose the host
Choose Connect GitLab…. Keep gitlab.com, or type your server under Host, such as
git.example.com. GitTree talks to that host only.Sign in with the browser
Choose Sign In with GitLab and approve GitTree on the page that opens. On a self-managed host, first fill OAuth application ID with the one registered there. Sign In with a Code Instead uses a one-time code.
Or use a token
Choose Enter a Personal Access Token…; Scopes the token needs says what to tick, and Open the Token Page opens it on your host.
Check the account
The account card shows … on … with your login and host.
Expected result
Merge requests, issues, pipelines and repositories of that GitLab host appear in GitTree.
If something goes wrong
“Enter the OAuth application ID your administrator registered on this host.”
Browser sign-in on a self-managed host needs its own OAuth application. Ask your administrator for its ID, or use a personal access token.
“Access was refused on …”
The approval was declined on GitLab. Choose Start Over and approve it.
Questions
Can I connect gitlab.com and a company GitLab at the same time?
Yes. Each host is its own account; Connect Another GitLab Account… adds more.