Since 518a1a0 a missing forge credential disables the forge instead of stopping archied. resolveForge returns an empty token in that case and cmd/archied/main.go still hands it to worktree.Manager{Token: token}. If repos are configured while the forge is disabled, clone/push fails at push time rather than at startup. This is the intended trade -- a deferred error beats a crash loop -- but the failure is currently discovered late and its message will not explain that the cause is an unconfigured forge.
Acceptance Criteria
A worktree operation attempted with no forge credential fails with a message naming the missing forge configuration as the cause, rather than a bare git transport error. Alternatively the manager refuses the operation up front. Either way the operator can tell why from the error alone.
Imported from beads archie-core-1786637490974-45-ede6ebfa · GitHub #66 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08
Since 518a1a0 a missing forge credential disables the forge instead of stopping archied. resolveForge returns an empty token in that case and cmd/archied/main.go still hands it to worktree.Manager{Token: token}. If repos are configured while the forge is disabled, clone/push fails at push time rather than at startup. This is the intended trade -- a deferred error beats a crash loop -- but the failure is currently discovered late and its message will not explain that the cause is an unconfigured forge.
### Acceptance Criteria
A worktree operation attempted with no forge credential fails with a message naming the missing forge configuration as the cause, rather than a bare git transport error. Alternatively the manager refuses the operation up front. Either way the operator can tell why from the error alone.
---
_Imported from beads `archie-core-1786637490974-45-ede6ebfa` · GitHub #66 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam
added the mediumbug labels 2026-10-27 13:36:52 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Since 518a1a0 a missing forge credential disables the forge instead of stopping archied. resolveForge returns an empty token in that case and cmd/archied/main.go still hands it to worktree.Manager{Token: token}. If repos are configured while the forge is disabled, clone/push fails at push time rather than at startup. This is the intended trade -- a deferred error beats a crash loop -- but the failure is currently discovered late and its message will not explain that the cause is an unconfigured forge.
Acceptance Criteria
A worktree operation attempted with no forge credential fails with a message naming the missing forge configuration as the cause, rather than a bare git transport error. Alternatively the manager refuses the operation up front. Either way the operator can tell why from the error alone.
Imported from beads
archie-core-1786637490974-45-ede6ebfa· GitHub #66 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08