Skip to content

Document recovery procedure for failed finalize operations #25

@ArjenSchwarz

Description

@ArjenSchwarz

Context

From code review of #21 (multi-spec comparison feature).

Current Behavior

If Finalize fails during the rebase/merge operation (internal/variants/manager.go:458), the repository could be left in an inconsistent state. The error handling in cmd/orbit/finalize.go:131-138 provides some guidance, but recovery steps aren't fully documented.

Suggested Improvements

  1. Add detailed recovery instructions to error messages
  2. Document manual recovery steps in README or help text
  3. Consider adding a orbit recover command for common failure scenarios
  4. Potentially wrap rebase in a transaction-like pattern with automatic rollback

Priority

Low - failures are rare and users can recover manually with git knowledge.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions