GitKraken allows you to connect to GitLab Self-Managed (CE or EE), which will help you find repos when cloning or adding your remotes.
- Create repositories on GitLab Self-Managed server including .gitignore and license
- Automatically generate an SSH key pair and add it to GitLab Self-Managed
- Save authentication into profiles
- Clone from GitLab Self-Managed repo list
- Add remotes for GitLab Self-Managed repos
- Create and view Pull Requests
- Work with GitLab Self-Managed Issues
GitLab Self-Managed Authentication
To authenticate with GitLab Self-Managed, navigate to the upper right corner to access Preferences Integrations.
Or alternatively if you are in the New Tab view, click on Preferences under Customize.
From the Integrations window, enter your Host Domain, then click the Generate a token on GitLab link. Note the permissions that need to be assigned to the token on your GitLab Self-Managed server.
This opens a web browser where you will log in with your GitLab Self-Managed credentials and generate an access token.
GitKraken needs the token to have
read_user scope and we recommend leaving the Expiration field blank.
Copy your token to the clipboard as this is the only time you will see this token. Paste the token into GitKraken and click on .
Generating an SSH Key for GitLab Self-Managed
Note 📝 - GitKraken uses your SSH key defined in Preferences SSH for git operations unless you set up a GitLab-specific SSH key, or enable your local SSH Agent.
Once your GitLab Self-Managed account has been connected to GitKraken, you may easily generate an SSH key and add it to your GitLab Self-Managed account from Preferences Integrations.
Click the button and watch the magic happen.
Alternatively add existing SSH Defaults with or an existing key pair through Add existing SSH key.
Share these resources with your team to explain why collaborating with GitKraken is easier, and to get everyone up and running with GitLab and GitKraken quickly.