merge: resolve v1.22.2 conflicts with custom

Per Q4 resolution (documented on kanban t_83741c53):
- .github/workflows/*: KEEP custom deletion (fork uses Gitea Actions under .gitea/workflows)
- ChatInput.tsx: KEEP custom forge picker states + provider-aware linkedPr
- WorkStatusContextSection.tsx: combine imports (WorkStatusPill + useConfigStore)
- WorkStatusPrimaryGroup.tsx: upstream nested-git/bootstrap-gate base + custom GitLab/Gitea forge rows
- NewWorktreeDialog.tsx: combine dialogs; keep custom MR/PR branch resolution
- SettingsView.tsx: custom deps minus undefined openThirdPartyProviderSetup
- search.ts + search.test.ts: KEEP upstream (enter-to-send, large-text-paste, first-party integrations)
- tr.ts: drop 4 auto-merge duplicate gitView.empty.* keys
This commit is contained in:
2026-09-06 10:55:54 +00:00
220 changed files with 45375 additions and 3531 deletions
+31
View File
@@ -0,0 +1,31 @@
---
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
+15
View File
@@ -308,6 +308,21 @@
"tr": "GitHub issue'ları ve PR'lar"
}
},
{
"label": "GitLab Issues & MRs",
"link": "/gitlab/",
"translations": {
"uk": "Завдання та MR GitLab",
"zh-CN": "GitLab 工单与 MR",
"es": "Issues y MRs de GitLab",
"pt-BR": "Issues e MRs do GitLab",
"ko": "GitLab 이슈 및 MR",
"pl": "Zgłoszenia i MR-y GitLab",
"fr": "Issues et MR GitLab",
"ja": "GitLab Issues と MR",
"de": "GitLab-Issues und MRs"
}
},
{
"label": "Magic Prompts",
"link": "/magic-prompts/",