2.6 KiB
| stage | group | info |
|---|---|---|
| Ecosystem | Integrations | To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments |
GitHub project integration (PREMIUM)
Introduced in GitLab Premium 10.6.
GitLab provides an integration for updating the pipeline statuses on GitHub. This is especially useful if using GitLab for CI/CD only.
This project integration is separate from the instance wide GitHub integration and is automatically configured on GitHub import.
Configuration
This integration requires a GitHub API token
with repo:status access granted.
Complete these steps on GitHub:
- Go to your Personal access tokens page at https://github.com/settings/tokens.
- Select Generate new token.
- Under Note, enter a name for the new token.
- Ensure that
repo:statusis checked and select Generate token. - Copy the generated token to use in GitLab.
Complete these steps in GitLab:
- Go to the project you want to configure.
- Go to the Integrations page
- Select GitHub.
- Ensure that the Active toggle is enabled.
- Paste the token you generated on GitHub.
- Enter the path to your project on GitHub, such as
https://github.com/username/repository. - (Optional) To disable static status check names, clear the Static status check names checkbox.
- Select Save changes or optionally select Test settings.
After configuring the integration, see Pipelines for external pull requests to configure pipelines to run for open pull requests.
Static / dynamic status check names
- Introduced in GitLab 11.5: using static status check names as opt-in option.
- In GitLab 12.4, static status check names is default behavior for new projects.
This makes it possible to mark these status checks as Required on GitHub.
When Static status check names is enabled on the integration page, your GitLab instance host name is appended to a status check name.
When disabled, it uses dynamic status check names and appends the branch name.