Repository navigation
GitLab forge support for PRs, CI badges, planboard and issue ingestion #193
Description
What competitors do
Emdash ingests issues from GitLab and Forgejo and runs a GitLab MR flow (README); Vibe Kanban integrates Azure Repos (docs).
Solenta today
GitHub-only by explicit guard: isGitHubRemote rejects gitlab/ssh/local remotes (electron/worktrees.js:974) and tests assert GitLab URLs parse to null (electron/test/issues.test.js:58). PR, CI badges, planboard and issue ingestion all assume gh. Broader than the Linear issue-ingestion ticket (#169): this is the PR/CI/planboard path.
Why it matters
Both surviving open-source competitors treat multi-forge as table stakes; a meaningful slice of the self-hosting dev audience is on GitLab.
Fix direction
Abstract the forge behind the gh-shaped seams (issues.js, prStatus/createPr, checks); add a GitLab backend via glab or the GitLab API with the same contract.
Activity
currentbits commentedon Aug 17, 2026
Deep-dive detail (T3 PR #4849): a capability-declared SCM provider interface — each host declares patch/comment/verdict/merge-strategy support and the UI renders only what will not fail. The way to add GitLab/Bitbucket/Azure without lowest-common-denominator UX.
currentbits commentedon Aug 18, 2026
Round-19: T3 Code already treats GitLab as one of four forges, not the second one (https://github.com/pingdotgg/t3code/blob/main/docs/user/source-control.md). GitHub / GitLab / Bitbucket / Azure DevOps share clone, publish, and PR create. Cursor mobile added Bitbucket + Azure DevOps on 29 Jul.
When this issue is built, keep the adapter seam wide enough that Bitbucket and Azure DevOps are more forges on the same PR/clone/publish layer, not a third copy of planboard. Planboard stays GitHub-native on purpose.
currentbits commentedon Aug 18, 2026
Round 23 intel: Factory v0.186.0 recognizes GitHub Enterprise and self-hosted GitLab remotes as first-class Git remotes, and v0.190.0 fixed per-host auth ("GitLab commands now authenticate against the host you are working with instead of a single default"). The per-host credential keying is the detail Solenta must get right when this lands: enterprise users routinely have gitlab.com plus one or more self-hosted instances, and a single default token leaks credentials across hosts. Host-scoped token storage from day one.
GitLab forge support for PRs, CI badges, planboard and issue ingestion (