docs(multi-forge): add runbook + adoption guide (MF-9) #310
No reviewers
Labels
No labels
area:agents
area:dashboard
area:database
area:design
area:design-review
area:flows
area:infra
area:meta
area:security
area:sessions
area:webhook
area:workdir
security
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks!310
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/300-mf9-multi-forge-docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
docs/multi-forge.mdrunbook covering operator overview, step-by-step adoption for a GitHub repo and a GitLab repo, cross-forge routing matrix (deps, label IDs, auth scheme, review model, squash merge, webhook sig), troubleshooting of real startup-validator / adapter error strings, and the per-forge webhook-secret uniqueness requirement (plus theFORGEJO_ACCESS_TOKENscoping note).CLAUDE.mdgains a one-line pointer under a new Multi-forge section, mirroring the existing Multi-repo / Penpot sections.token_files,github_webhook_secret_file,gitlab_webhook_secret_file) and actual source paths (adapter-factory.ts,webhook-config.ts,agent-runner.ts,gitlab-adapter.ts).Test plan
docs/multi-forge.mdrenders correctly on forge.jacquin.app (headings, tables, code fences, relative links tomulti-repo.mdand../specs/multi-forge.md).CLAUDE.mdMulti-forge section renders with a working link todocs/multi-forge.md.Closes #300