archied: [[repos]] entries can't span more than one forge #948

Closed
opened 2026-10-27 13:38:25 +00:00 by sam · 0 comments
Owner

[forge] is a single top-level block resolved once (resolveForge in cmd/archied/main.go:332) into one forge.Forge client, shared by every entry in [[repos]]. The Repo struct (internal/config/config.go:56) has no per-repo type/host/token override -- owner/name are the only identity fields, so every repo is assumed to live on whatever single forge the daemon is configured for.

This blocks a [[repos]] list spanning more than one forge (e.g. one repo on GitHub, another on a Gitea instance) under a single archied identity. Discovered live on carina 2026-08-09: switching [forge] to type = "github" for archie-core made the daemon start querying the tau repo entry (still Gitea-hosted) against api.github.com, producing repeated 404s (get repo sam/tau: GET https://api.github.com/repos/sam/tau: 404 Not Found) until the tau entry was removed as a workaround.

Expected

Each [[repos]] entry should be able to declare (or inherit a default) its own forge type/host/token, and the daemon should resolve a forge client per repo rather than one globally, so repos on different forges can be dispatched from the same archied instance.

Workaround in place

tau's [[repos]] entry was removed from carina's config.toml so archie-core (now GitHub) doesn't try to poll it against the wrong forge. tau gets no automated dispatch from this instance until this is fixed or it gets a separate identity.

Close reason

Superseded by the identities feature, not fixed via the originally-requested per-repo-within-one-repos-list forge override. Verified: IdentityConfig (internal/config/config.go:549) gives each identity its own Forge + Repos list, bootstrap.go:820 builds a per-identity runner with its own forge client, and deployments/multi-forge-github-gitea.toml is a documented, supported profile for exactly the carina/tau scenario this bug describes (GitHub + Gitea from one daemon). The bug's own workaround note anticipated this: 'tau gets no automated dispatch...until this is fixed or it gets a separate identity' -- separate identity is now the supported path. A single identity still cannot mix forges within one flat repos list; reopen if that finer granularity is specifically wanted.


Imported from beads archie-core-1786637500900-420-335d8bbb · GitHub #441 · type bug · priority P2 · created 2026-08-08 · closed 2026-09-02

`[forge]` is a single top-level block resolved once (`resolveForge` in `cmd/archied/main.go:332`) into one `forge.Forge` client, shared by every entry in `[[repos]]`. The `Repo` struct (`internal/config/config.go:56`) has no per-repo `type`/`host`/`token` override -- `owner`/`name` are the only identity fields, so every repo is assumed to live on whatever single forge the daemon is configured for. This blocks a `[[repos]]` list spanning more than one forge (e.g. one repo on GitHub, another on a Gitea instance) under a single archied identity. Discovered live on carina 2026-08-09: switching `[forge]` to `type = "github"` for `archie-core` made the daemon start querying the `tau` repo entry (still Gitea-hosted) against `api.github.com`, producing repeated 404s (`get repo sam/tau: GET https://api.github.com/repos/sam/tau: 404 Not Found`) until the `tau` entry was removed as a workaround. ### Expected Each `[[repos]]` entry should be able to declare (or inherit a default) its own forge type/host/token, and the daemon should resolve a forge client per repo rather than one globally, so repos on different forges can be dispatched from the same archied instance. ### Workaround in place `tau`'s `[[repos]]` entry was removed from carina's `config.toml` so `archie-core` (now GitHub) doesn't try to poll it against the wrong forge. `tau` gets no automated dispatch from this instance until this is fixed or it gets a separate identity. ### Close reason Superseded by the [[identities]] feature, not fixed via the originally-requested per-repo-within-one-[[repos]]-list forge override. Verified: IdentityConfig (internal/config/config.go:549) gives each identity its own Forge + Repos list, bootstrap.go:820 builds a per-identity runner with its own forge client, and deployments/multi-forge-github-gitea.toml is a documented, supported profile for exactly the carina/tau scenario this bug describes (GitHub + Gitea from one daemon). The bug's own workaround note anticipated this: 'tau gets no automated dispatch...until this is fixed or it gets a separate identity' -- separate identity is now the supported path. A single identity still cannot mix forges within one flat [[repos]] list; reopen if that finer granularity is specifically wanted. --- _Imported from beads `archie-core-1786637500900-420-335d8bbb` · GitHub #441 · type bug · priority P2 · created 2026-08-08 · closed 2026-09-02_
sam added the mediumbug labels 2026-10-27 13:38:25 +00:00
sam self-assigned this 2026-10-27 13:38:25 +00:00
sam closed this issue 2026-10-27 13:38:25 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#948