Source control integrations can be configured for both Self-Hosted Runners and Gitpod Desktop. You can set up a GitHub integration during runner creation or in the runner settings. Self-hosted GitHub instances are supported by changing the Host during setup.
You can skip this step if someone has already set up the runner for you and SCM integration with GitHub has already been configured. In that case, you can go directly to Authorizing GitHub Access. This step allows administrators to configure what authorization methods (OAuth, PATs) and SCM providers (GitHub, GitLab, Bitbucket, Azure DevOps) will be available for authorization.
For self-hosted runners (like AWS), GitHub integration is configured during runner creation or in the runner settings.
There are two ways to integrate with GitHub. Both can be used simultaneously:
Add new provider
Enable GitHub OAuth
Add new provider
Enable GitHub PAT
For Gitpod Desktop, GitHub authentication is managed through organization settings:
github.com
is configured by defaultDesktop Settings
The first time a user creates an environment, they will be asked to enter a Personal Access Token.
Set GitHub PAT
After creating the token, return to the dialog and paste the token.
The environment will now be created using the provided token.
Source control integrations can be configured for both Self-Hosted Runners and Gitpod Desktop. You can set up a GitHub integration during runner creation or in the runner settings. Self-hosted GitHub instances are supported by changing the Host during setup.
You can skip this step if someone has already set up the runner for you and SCM integration with GitHub has already been configured. In that case, you can go directly to Authorizing GitHub Access. This step allows administrators to configure what authorization methods (OAuth, PATs) and SCM providers (GitHub, GitLab, Bitbucket, Azure DevOps) will be available for authorization.
For self-hosted runners (like AWS), GitHub integration is configured during runner creation or in the runner settings.
There are two ways to integrate with GitHub. Both can be used simultaneously:
Add new provider
Enable GitHub OAuth
Add new provider
Enable GitHub PAT
For Gitpod Desktop, GitHub authentication is managed through organization settings:
github.com
is configured by defaultDesktop Settings
The first time a user creates an environment, they will be asked to enter a Personal Access Token.
Set GitHub PAT
After creating the token, return to the dialog and paste the token.
The environment will now be created using the provided token.