GitLab

Partial. GitLab repository binding is available. Issue tracker support is coming soon; use Linear or Jira for issue management in the meantime.

The GitLab integration enables workflows to bind to GitLab repositories and access repository content. Full issue tracker support (issue CRUD, comments, transitions) is in progress.

What you can do (today)

Repository binding: link a Rensei project to a GitLab repository
Git operations: agents can clone, read, and commit code (via the main Git provider)
Webhook ingestion: receive repository events (push, merge request) and trigger workflows

What's coming soon

Issue tracker: create, update, search GitLab issues
Merge requests: full MR lifecycle management
CI/CD pipelines: trigger and monitor GitLab CI pipelines

Repository credential setup

Create a GitLab Personal Access Token

For GitLab Cloud:

Go to gitlab.com/-/user_settings/personal_access_tokens

For self-hosted GitLab:

Go to https://gitlab.mycompany.com/-/user_settings/personal_access_tokens

Then: 2. Token name: e.g., "Rensei" 3. Scopes:

read_repository - read repository content
write_repository - push commits and branches
api - full API access (required for future issue tracker support)

Copy the token

Add the token to Rensei

In Rensei, go to Settings → Integrations (or bind during project setup)
Select GitLab as the repository provider
Paste your Personal Access Token
For self-hosted GitLab, enter your instance URL: https://gitlab.mycompany.com
Click Connect

The platform validates the token and stores it encrypted.

Current repository binding

When you bind a GitLab repository to a Rensei project:

Workflows can reference {{ $repo.file }} to read repository content
Agents can commit code and push branches
Generic git nodes (branch creation, file operations) work with GitLab

Example workflow with GitLab:

steps:
  - id: read_config
    type: github.file.read  # Works with GitLab too
    inputs:
      repo: "mygroup/myproject"
      path: "config.yml"

  - id: validate
    type: condition
    condition: "{{ $steps.read_config.contents | length > 0 }}"
    onTrue: [commit_changes]

Issue tracker (coming soon)

Once the GitLab issue tracker is fully implemented, you will be able to:

Create GitLab issues from workflows
Search and update issues
Transition issues through custom workflows
Post comments

Track progress on the coverage matrix.

Self-hosted GitLab

If you use a self-hosted GitLab instance:

When entering your Personal Access Token, specify your instance URL: https://gitlab.mycompany.com
Platform will validate against your instance's API

Limitations

Issue tracker: Not yet supported; use Linear, Jira, or Asana
Webhooks: Repository events are received but not yet exposed as workflow triggers
Approvals: GitLab's approval rules are not yet integrated with Rensei approval gates
CI/CD: GitLab CI pipelines cannot yet be triggered or monitored from workflows

Troubleshooting

"Authentication failed"

Verify your Personal Access Token is still valid
Check the token has not been revoked in your GitLab profile
Ensure the token has the read_repository or api scope
For self-hosted GitLab, verify your instance URL is correct

"Repository not found"

Verify the repository path is correct (e.g., mygroup/myproject)
Ensure you have access to the repository in GitLab
For self-hosted GitLab, verify the instance URL matches your GitLab instance

Next steps

GitHub integration - For repository operations today
Repository binding - Bind GitLab repos to Rensei projects
Workflow triggers - Set up event-based automation
Check back soon for full GitLab issue tracker support

On this page