Gitpod works nicely with GitLab: You can start Gitpod workspaces directly from the web pages of your GitLab repositories, and you can configure Gitpod to automatically prebuild these workspaces such that you can start coding on any branch in no time.
To use Gitpod on GitLab repositories, you have to link your GitLab account to Gitpod. Gitpod redirects you to GitLab’s authentication workflow when needed. Alternatively, you might want to connect your GitLab account manually.
All of this is already pre-configured for GitLab.com
(the SaaS version), and can easily be set up for self-hosted GitLab installations.
You can start a Gitpod workspace directly from the web pages of a GitLab repository. Simply click on the dropdown arrow next to the Web IDE split button on the project or merge request page, and choose Gitpod. The Gitpod workspace will open in a new browser tab. The next time you visit a GitLab page, the last used action will be pre-selected.
GitLab Integration
To launch new Gitpod workspaces for issues, branches, specific commits, etc. you can also prefix any GitLab URL with gitpod.io/#
as described in the Getting started page, or use the browser extension to add a convenient Gitpod button to every GitLab page.
To use Gitpod on a GitLab repository, you have to connect your GitLab account with your Gitpod account. In the following, we assume that you already have a valid account on the GitLab instance you want to connect to.
Gitpod supports the following use cases:
If you have initially logged into Gitpod using GitLab
, your Gitpod account is already connected to your GitLab.com
account and you can skip this section.
If you have logged into Gitpod with a different provider, you can manually add your GitLab account as follows:
GitLab integration connect menu item
You will be redirected to GitLab’s login page. Log in with your username and password or choose one of the OAuth providers from the list.
Once logged in successfully, you will be asked to authorize Gitpod to access your personal information on GitLab and use their API. Click Authorize.
GitLab: Authorize Gitpod
GitLab integration connected
A Self-Hosted GitLab installation has to be registered to Gitpod before it can be used. Once that’s done, you can link your GitLab account on that installation to Gitpod using the following steps:
To disconnect a GitLab account from your Gitpod account:
This will only invalidate the current access token in Gitpod. To disable access for good you have to revoke the access to Gitpod on the GitLab side.
The SaaS service GitLab.com
is already pre-configured in Gitpod. But if you are using a Self-Hosted GitLab installation, you have to register it in Gitpod before it can be used.
Here is how to register your Self-Hosted GitLab installation:
Git Integrations
and click on the “New Integration” button.Git Integrations section in the Gitpod settings
New Git integration dialog
The next field in the form is the redirect URL using which you register Gitpod on the GitLab side. Copy the redirect URL to your clipboard using the button on the right.
Go to /-/user_settings/applications
on your GitLab installation to create an OAuth app. If desired, this can also be achieved with a group-owned or instance-wide OAuth app when you don’t want your application to only be owned by one user acccount. Type in a name (e.g. “Gitpod”) and paste the redirect URL in the corresponding text area. Check the api, read_user and read_repository scopes and click on Save Application.
Create new GitLab app
New GitLab app created
On your GitLab installation, you can enable the native Gitpod integration as described in the GitLab docs. This will add a Gitpod button to your GitLab repository pages for a seamless workspace creation experience, as can be seen in the Starting Workspaces section.
Gitpod works nicely with GitLab: You can start Gitpod workspaces directly from the web pages of your GitLab repositories, and you can configure Gitpod to automatically prebuild these workspaces such that you can start coding on any branch in no time.
To use Gitpod on GitLab repositories, you have to link your GitLab account to Gitpod. Gitpod redirects you to GitLab’s authentication workflow when needed. Alternatively, you might want to connect your GitLab account manually.
All of this is already pre-configured for GitLab.com
(the SaaS version), and can easily be set up for self-hosted GitLab installations.
You can start a Gitpod workspace directly from the web pages of a GitLab repository. Simply click on the dropdown arrow next to the Web IDE split button on the project or merge request page, and choose Gitpod. The Gitpod workspace will open in a new browser tab. The next time you visit a GitLab page, the last used action will be pre-selected.
GitLab Integration
To launch new Gitpod workspaces for issues, branches, specific commits, etc. you can also prefix any GitLab URL with gitpod.io/#
as described in the Getting started page, or use the browser extension to add a convenient Gitpod button to every GitLab page.
To use Gitpod on a GitLab repository, you have to connect your GitLab account with your Gitpod account. In the following, we assume that you already have a valid account on the GitLab instance you want to connect to.
Gitpod supports the following use cases:
If you have initially logged into Gitpod using GitLab
, your Gitpod account is already connected to your GitLab.com
account and you can skip this section.
If you have logged into Gitpod with a different provider, you can manually add your GitLab account as follows:
GitLab integration connect menu item
You will be redirected to GitLab’s login page. Log in with your username and password or choose one of the OAuth providers from the list.
Once logged in successfully, you will be asked to authorize Gitpod to access your personal information on GitLab and use their API. Click Authorize.
GitLab: Authorize Gitpod
GitLab integration connected
A Self-Hosted GitLab installation has to be registered to Gitpod before it can be used. Once that’s done, you can link your GitLab account on that installation to Gitpod using the following steps:
To disconnect a GitLab account from your Gitpod account:
This will only invalidate the current access token in Gitpod. To disable access for good you have to revoke the access to Gitpod on the GitLab side.
The SaaS service GitLab.com
is already pre-configured in Gitpod. But if you are using a Self-Hosted GitLab installation, you have to register it in Gitpod before it can be used.
Here is how to register your Self-Hosted GitLab installation:
Git Integrations
and click on the “New Integration” button.Git Integrations section in the Gitpod settings
New Git integration dialog
The next field in the form is the redirect URL using which you register Gitpod on the GitLab side. Copy the redirect URL to your clipboard using the button on the right.
Go to /-/user_settings/applications
on your GitLab installation to create an OAuth app. If desired, this can also be achieved with a group-owned or instance-wide OAuth app when you don’t want your application to only be owned by one user acccount. Type in a name (e.g. “Gitpod”) and paste the redirect URL in the corresponding text area. Check the api, read_user and read_repository scopes and click on Save Application.
Create new GitLab app
New GitLab app created
On your GitLab installation, you can enable the native Gitpod integration as described in the GitLab docs. This will add a Gitpod button to your GitLab repository pages for a seamless workspace creation experience, as can be seen in the Starting Workspaces section.