Importing GitHub project using GitHub integration or token doesn't configure GitHub project integration
Summary
There are two primary methods for importing GitHub projects to GitLab.com:
- Using the GitHub integration, and
- Using a GitHub token
Documentation on GitHub project integration states
This project integration is separate from the instance wide GitHub integration and is automatically configured on GitHub import.
After importing a GitHub project (either through the UI or via API) to GitLab.com (12.1.0-pre 7d840e4bbeb
), the project integration isn't configured, contrary to the documentation. I'm not sure whether this is broken functionality or if the documentation needs to be updated.
Curiously, a pull mirror is created but disabled, with an alert that reads Disabled mirrors can only be enabled by instance owners. It is recommended that you delete them.
.
Steps to reproduce
- Create a repository on GitHub.com
- Import that project to GitLab using the
Import project from GitHub
option
Example Project
-
https://gitlab.com/gitlab-silver/GitHub-project-import-via-UI
- Imported from GitHub using a GitHub token via the UI.
- A pull mirror is created, but disabled
- The GitHub project integration is not configured and remains inactive
-
https://gitlab.com/gitlab-silver/GitHub-project-import-via-API
- Imported from GitHub using a GitHub token via the API.
- A pull mirror is created, but disabled
- The GitHub project integration is not configured and remains inactive
-
https://gitlab.com/gitlab-silver/GitHub-project-import-via-UI-CI-CD-for-external-repo
- Imported from GitHub using the CI/CD for external repositories option.
- A pull mirror is created and functioning properly
- The GitHub project integration is configured and active
What is the current bug behavior?
The GitHub project integration is not configured and remains inactive
What is the expected correct behavior?
According to the documentation, the GitHub project integration should be configured and active
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com (12.1.0-pre 7d840e4bbeb
)