Skip to content

Pre-flight validation before rebase operations #12

Description

@dezren39

Rebase failures mid-stack are painful to recover from. Add checks before starting any rebase:

  1. Merge commits in feature branches — detect with git rev-list --merges, warn and abort unless --force
  2. Stale metadata — detect when parent_head doesn't match reality after out-of-band operations
  3. ez move stale history — check ancestor relationship before replaying commits
  4. Cherry pre-check — use git cherry to find redundant commits before rebasing; skip rebase entirely if all redundant

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