Add GitLab Cloud and GitLab Self-Hosted to Enterprise Integrations page

Open Beginner friendly
#575 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
75/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
documentation

Research direction

Open the Enterprise Integrations page linked in the issue and find the current Source Control integration list. Update it to name GitLab (gitlab.com) and GitLab Self-Hosted, then verify the rendered page clearly communicates the relevant OHE and SaaS/Cloud support distinctions described in the issue.

Written by the indexing model from the issue text.

Description

documentation enterprise

Summary

Update the Enterprise Integrations page to clearly specify which GitLab variants are supported on OHE vs SaaS/Cloud.

Current State

The page currently says:

Source Control: GitHub Enterprise, GitLab, and Bitbucket Data Center

This is ambiguous about:

  • Whether "GitLab" means gitlab.com (cloud) or self-hosted
  • Which variants are supported on which product (OHE vs SaaS)

Requested Changes

Clarify the text to be:

Source Control: GitHub Enterprise, GitLab (gitlab.com), GitLab Self-Hosted, and Bitbucket Data Center

Context

Internally, GitLab Self-Hosted is supported on OHE (not SaaS/Cloud). We should make this clearer in the docs to avoid prospect confusion.

Acceptance Criteria

  • Update integration list to explicitly mention both GitLab cloud and self-hosted variants
  • Consider adding a note or table clarifying which integrations are supported on which product (OHE vs SaaS/Cloud)

References

Dominant language
MDX
Stars
12
Forks
55
Avg merge
1d 6h
Merged PRs (30d)
32

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenHands/docs

All issues in OpenHands/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.