Skip to content

Support push --force-with-lease semantics #22

Description

@odrobnik

MissionControl's GitKit migration still keeps git push --force-with-lease origin <branch> as a shell fallback.

GitKit exposes Repository.push(...), including force refspecs, but MC needs real force-with-lease protection for auto-rebased agent branches: the push must fail if the remote branch advanced unexpectedly since the local lease was observed.

Needed surface: a GitKit push API that can express force-with-lease semantics, or an equivalent compare-and-push primitive that preserves the race protection of git push --force-with-lease.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions