integrationsPage.detail.h1

Repositories, issues and merge requests, on request.

The self-hosted end of the same problem.

If your engineering runs on GitLab — often because it is self-hosted — connecting it puts repositories, issues and merge requests in reach of the assistant.

integrationsPage.detail.overview

GitLab tends to be chosen for control: a company that wants its source on its own infrastructure, or one whose CI and code live deliberately in the same place.

Property groups that own their booking platform sometimes fall into that category, particularly where a data protection requirement makes self-hosting the simpler answer than a policy argument.

Connecting GitLab gives that team the same conversational reach as everyone else — what is open, what is waiting, what changed — without asking them to abandon the setup they chose for good reasons. Like the rest of this category, it serves your engineers rather than your operations.

The practical test is whether anyone in your company writes code. If nobody does, skip this one — there is no property-management benefit hiding underneath it, and a page that pretended otherwise would be wasting your time.

integrationsPage.detail.capabilities

Once GitLab is connected, ProhostAI works with your projects, issues and merge requests in plain language.

Read

  • Search projectsFind code and history across the projects the connected account can reach. “What is waiting for review on the portal project?”
  • Review issues and MRsSee what is open and what has stalled.

Create & update

  • Create and update issuesRaise or update issues as work is identified.
  • Comment on merge requestsLeave a note without switching context.

integrationsPage.detail.howToConnect

GitLab connects through OAuth, against gitlab.com or a self-hosted instance reachable from the internet.

  1. 1Open ProhostAI and go to Settings → Connections.
  2. 2Search for GitLab and select Connect.
  3. 3Sign in to GitLab and approve the permissions.
  4. 4Ask what is open on one of your projects to confirm it works.

integrationsPage.detail.goodToKnow

Self-hosted instances work, provided the instance is reachable from the internet for the OAuth flow.

Access follows the connected account’s project permissions.

This is a tool for your engineering team rather than property operations.

integrationsPage.detail.faqTitle

Yes, provided the instance is reachable from the internet so the OAuth connection can complete.

Those the connected account can access. Project permissions continue to apply.

Yes, and update them, and comment on merge requests, within that account’s access.

No. It serves the engineering team at companies that build their own software.

Open Settings → Connections in ProhostAI and disconnect it, or revoke the application in your GitLab settings.

Reach the code without the context switch