Fail refresh when the configured base cannot resolve #30

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

Prepared worktrees currently swallow every resolveBase error and report successful refresh against stale history.

Acceptance criteria

Prepared-worktree refresh returns a contextual error for a missing, renamed, or invalid base; fresh and reused Prepare paths have consistent tests.

Close reason

Fixed on main: prepared-worktree refresh now returns the resolveBase error instead of swallowing it (worktree.go:253-258, 'a missing base is configuration or repository drift and must fail closed'); resolveBase tries the qualified remote ref then origin/ and errors otherwise.


Imported from beads archie-core-1ysw.4 · GitHub #601 · type bug · priority P2 · created 2026-08-22 · closed 2026-08-24

Prepared worktrees currently swallow every resolveBase error and report successful refresh against stale history. ### Acceptance criteria Prepared-worktree refresh returns a contextual error for a missing, renamed, or invalid base; fresh and reused Prepare paths have consistent tests. ### Close reason Fixed on main: prepared-worktree refresh now returns the resolveBase error instead of swallowing it (worktree.go:253-258, 'a missing base is configuration or repository drift and must fail closed'); resolveBase tries the qualified remote ref then origin/<base> and errors otherwise. --- _Imported from beads `archie-core-1ysw.4` · GitHub #601 · type bug · priority P2 · created 2026-08-22 · closed 2026-08-24_
sam added the mediumbug labels 2026-10-27 13:34:40 +00:00
sam self-assigned this 2026-10-27 13:34:40 +00:00
sam closed this issue 2026-10-27 13:34:40 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#30