— INTEGRATION · GITLAB · PROJECT-SCOPED

Engineer Cyborg opens MRs in GitLab.

Reads issues, opens merge requests, reviews code, comments, runs CI pipelines. Self-hosted GitLab and gitlab.com both supported.

Self-hosted? Yes.

Self-hosted GitLab CE / EE behind your firewall is fully supported. The Cyborg authenticates via project access token; we maintain no inbound network path to your GitLab instance.

— 02 / CAPABILITIES

— WHAT THE CYBORG CAN DO IN GITLAB

Capabilities · scoped, audited.

CAP · CODE

Open merge requests

Pulls work from issues, writes code, runs tests locally, opens MR with full description + linked issue.

  • Branch from main / develop
  • Commit + push
  • MR with description + checklist
  • Link to source issue
CAP · REVIEW

Review others’ MRs

Line-by-line review with specific feedback. Approves trivial changes (T2); requests-changes on substance.

  • Inline comments
  • Suggest changes
  • Approve / request changes
  • CI check results review
CAP · CI

Trigger + debug pipelines

Runs pipelines on demand. Reads logs. Triages failures: real bug / flaky / infra. Files follow-up issues.

  • Manual + scheduled triggers
  • Log triage
  • Flake quarantine
  • Pipeline retry on transient errors
CAP · ISSUES

Read + comment on issues

Triages incoming issues, asks clarifying questions, links to related work, closes resolved ones.

  • Issue triage
  • Label management
  • Milestone updates
  • Cross-link to MRs

03OAuth + tokens.

Two auth modes:

  • OAuth 2.0 (gitlab.com or self-hosted with public OAuth) · standard flow; you grant scopes; tokens rotate.
  • Project Access Token (recommended for self-hosted) · you generate a token in GitLab with api + write_repository scopes for the specific project, paste it in the Cyborg dashboard.

Project Access Tokens are the recommended approach for enterprise setups — they’re project-scoped by definition, expire on a schedule you control, and don’t require any inbound connection.

04Setup · 5 minutes.

  • Step 01 · In GitLab, generate Project Access Token with api + write_repository scopes (Maintainer role).
  • Step 02 · Paste in Cyborg dashboard · Settings · Integrations · GitLab.
  • Step 03 · Pick which projects the Cyborg should read/write.
  • Step 04 · Cyborg reads project metadata + opens its first MR within minutes.

05FAQ.

Does this work behind a corporate firewall?+

Yes. The Cyborg makes outbound HTTPS connections to your GitLab; no inbound exposure required. Whitelist cyborg-egress.anilcyborg.com in your firewall’s outbound allow-list (only if your firewall blocks outbound by default).

What about merge protection rules?+

Honoured. The Cyborg cannot bypass branch protection. If main requires 2 reviewers, the Cyborg’s approval counts as one; humans must provide the second.

GitHub vs GitLab vs both?+

Both supported simultaneously. GitHub integration uses GitHub OAuth; this page covers GitLab. Same Cyborg can work in both.