Content
View differences
Updated by Maya Berdygylyjova about 2 years ago
Use the [GitHub integration documentation](https://www.openproject.org/docs/system-admin-guide/integrations/github-integration/) as foundation.
Add GitLab specific features, such as:
* [x] [ ] **Merge Requests** _(this is similar to GitHub pull requests)_
* [x] [ ] **Issues**
* [ ] **Pipelines** _(this is similar to GitHub Actions)_
* [x] [ ] **Git Snippets** _(agnostic for GitHub and GitLab)_
* [x] [ ] **Gitlab Bot User**_: Similar to Github integration / Also see https://github.com/btey/openproject-gitlab-integration?tab=readme-ov-file#the-gitlab-bot-user-in-openproject_
Include the following configuration guides for system admins
* [ ] Cover the case when a previous installation of the GitLab plugin existed with the following resolution steps
* [ ] Upon upgrading to the new OpenProject version with core GitLab integration, admins should remove the Git trace _modules/gitlab\_integration/.git_ as OpenProject core would have overwritten that directory
* [ ] OpenProject will show a sticky warning for admins IF it detects a previous installation- with instructions linked on how to resolve this issue.
* [ ] Reference the above in a troubleshooting section as well in case users miss the first notice
Add GitLab specific features, such as:
* [x]
* [x]
* [ ] **Pipelines** _(this is similar to GitHub Actions)_
* [x]
* [x]
Include the following configuration guides for system admins
* [ ] Cover the case when a previous installation of the GitLab plugin existed with the following resolution steps
* [ ] Upon upgrading to the new OpenProject version with core GitLab integration, admins should remove the Git trace _modules/gitlab\_integration/.git_ as OpenProject core would have overwritten that directory
* [ ] OpenProject will show a sticky warning for admins IF it detects a previous installation- with instructions linked on how to resolve this issue.
* [ ] Reference the above in a troubleshooting section as well in case users miss the first notice