bot-hermes
4ce02ee569
- Add codeberg.org to deriveLinkedIssueProvider built-in Gitea check - Fix Gitea PR review prompt: !N → #N (GitLab vs Gitea syntax) - Update gitlab.mdx: remove 'read-only' claim (write support ships) - Gate walkthrough Gitea PR source (server can't fulfill yet) - Thread per-project API base URL override into walkthrough GitLab diff - Stop following cross-origin redirects in GitLab/Gitea clients (auth leak prevention)
32 lines
1.5 KiB
Plaintext
32 lines
1.5 KiB
Plaintext
---
|
|
title: GitLab Issues & MRs
|
|
description: Connect GitLab and start sessions from issues and merge requests.
|
|
---
|
|
|
|
# GitLab Issues & MRs
|
|
|
|
Connect your GitLab account and OpenChamber can pull in issues and merge requests, and start a session straight from one. You can also create, update, and merge MRs directly from OpenChamber.
|
|
|
|
## Connect GitLab
|
|
|
|
1. Open **Settings → Git**.
|
|
2. Under GitLab, choose **Connect**.
|
|
3. Paste a Personal Access Token. Create one in GitLab under **Profile → Access Tokens** — the `read_api` scope is enough for read-only workflows, and `api` is needed later for writing.
|
|
4. For a self-hosted GitLab instance, also enter the instance URL (for example `https://gitlab.example.com`).
|
|
|
|
When it's connected, your account shows under the GitLab section. You can connect more than one account and switch between them, or disconnect at any time.
|
|
|
|
## Start work from an issue or MR
|
|
|
|
When you create a [worktree session](/worktrees/) with GitLab connected, you can choose **Start from GitLab issue/MR**:
|
|
|
|
- pick an **issue** and OpenChamber names the branch after it and opens the session with the issue and its comments as the first message
|
|
- pick a **merge request** and it checks out the MR's branch; you can include the MR's diff so the agent has the full change
|
|
|
|
This drops you straight into a session with the context already loaded.
|
|
|
|
## Related
|
|
|
|
- [Git & GitHub Workflows](/git/) — commit and manage branches
|
|
- [Worktree Sessions](/worktrees/) — where issue and MR sessions start
|