-
c12b921: Introduce the internal
CodeHostseam so stack orchestration can operate on GitHub pull requests and GitLab merge requests through provider adapters.The CLI now selects a provider at startup and uses host-neutral concurrency and polling configuration internally. Repair plumbing also records request source repositories and pushed remotes so fork-backed repairs can be recreated and undone safely. Provider adapters normalize missing historical changes before orchestration decides whether to recreate them, and enumerate open changes exhaustively so stale-metadata decisions never depend on arbitrary list caps. Provider adapters also share one in-memory contract implementation so additional hosts can reuse the same lifecycle behavior without copying adapter test seams. The new seam names hosted requests as changes internally while preserving the existing persisted
prkeys and exported pull-shaped models for compatibility. GitLab source-project enrichment is cached per adapter layer, including concurrent lookups for fork-backed requests. -
c12b921: Add GitLab support.
stacknow talks to GitLab merge requests through theglabCLI alongside GitHub pull requests viagh.- New
CodeHostGitLab.layershells out toglab mr ...andglab apiand maps GitLab'siid,source_branch,target_branch,web_url,description, andopened|merged|closed|lockedstate vocabulary onto the samePullRef/PullMetashapes the rest of the tool already understands. CodeHostGitLab.memorymirrorsCodeHostGitHub.memoryfor tests.CodeHostauto-detects exactgithub.comandgitlab.comremotes; an enterprise host is selected throughgit config stack.codeHost, withSTACK_CODE_HOSTavailable as a temporary override.- GitLab source projects are normalized for safe repair pushes from fork MRs.
- GitLab MR enumeration decodes paginated API output as NDJSON, and immediate merge disables deferred auto-merge so descendant repair only starts after a landed MR.
- GitLab MR target updates use
--yes, while description replacement and auto-merge useglab apiso repair never pauses for confirmation, can clear a description, and reliably requests server-side auto-merge. --adminis rejected before mutation on GitLab because there is noglabequivalent of GitHub's admin merge.
Stack orchestration remains code-host independent while preserving scoped repair, post-repair description refresh, and undo support for fork remote pushes.
- New
-
c12b921: User-facing polish for code-host-neutral wording.
- CLI help text, the
guidecommand, and the merge failure hint now talk about "changes" / "target branches" / "code-host auto-merge" instead of "PRs" / "PR bases" / "GitHub auto-merge". GitHub-specific behaviour (admin merge) is still called out where it applies. package.jsondescription and keywords mention GitLab and merge requests.- README, AGENTS.md (and the CLAUDE.md symlink), CONTEXT.md, and the
skills/stack/SKILL.mdagent guide document theCodeHostseam, the two backends (gh + glab), and code-host selection. The skill now shows GitLab equivalents in the Happy Path section and notes that--adminis GitHub-only. - Provider adapters normalize missing historical changes so GitLab
404 Not Foundresponses and GitHub lookup failures trigger the same safe recreation path.
- CLI help text, the
-
c12b921: Fix three rendering quirks surfaced by the GitLab smoke test.
stack syncagainst a GitLab remote now writes!1,!2,!3in the stack block inside each MR description so they render as real merge-request links on gitlab.com. Previously the block always used GitHub's#Nsyntax, which on GitLab refers to issues — so the references rendered as plain text or links to nonexistent issues. The completed-line parser instackBlockaccepts both#Nand!Nso blocks written by either code host are preserved on rewrite. The selectedCodeHostadapter supplies native reference rendering, including for explicitly configured enterprise hosts.- GitLab stack blocks now include MR titles beside
!Nreferences, including completed history when the MR can still be read, because GitLab only exposes the title on hover for bare!Nautolinks. GitHub keeps the compact#Nformat. stack statusnow labels the displayed trunk as the trunk actually used by the stack (e.g.mainwhen the stack lives offmain) instead of always usingcfg.trunks[0]. The inference falls back tocfg.trunks[0]when no trunk is referenced as a parent.stack mergenow reportswould switch to <actual trunk>and switches to the right trunk on apply, instead of unconditionally usingcfg.trunks[0]. Same fix instack undo: the trunk to switch to is inferred from the savedrun.state.links.
The first item is genuinely GitLab-specific; the other two were pre-existing display bugs that affect any repo whose trunk is not
dev. -
1b4221c: Scope repair, final merge diagrams, and stack-block refreshes to the selected stack, update blocks for requests recreated during repair, keep sync dry-runs free of fetch mutations, use tracked change identities when fork heads share a branch name, and checkpoint repair mutations so failed merge and sync attempts can be undone safely.
-
1be576f: Limit the final merge repair diagram to the selected stack.
-
5510fb4: Upgrade toolchain: TypeScript 6.0, vitest 4.1, oxlint 1.66, oxfmt 0.51.
- Scope
stack syncto the current or requested stack, and add keep-going sync for independent stacks.
- Improve sync output, remove the public repair command, and add oxlint/oxfmt checks.
- Add
stack merge --auto --through <branch-or-pr>for bounded auto-merge ranges.
- Initial public release.