History replacement

History replacement is an explicit operation for replacing the repository's reachable Git history. It is not a force push to protected main.

Start an attempt

An actor with the required read, write and replacement authority starts an attempt. Use the returned staging instructions and retain its public attempt ID. The current generation remains the reference until completion is confirmed.

Stage and complete

Upload the intended history to the staging location documented by the service, then request completion of that same attempt. Completion fences the old generation before publishing the replacement. Refresh an uncertain outcome rather than starting a competing attempt.

Abort

Abort an open attempt only when the service offers that action. Review the attempt ID first. A completed replacement cannot be undone by an abort request.

Inspect status

Open, completing, completed and absent-attempt states are different. A load error is not evidence that no attempt exists. Old-generation credentials, content references and pull requests cannot silently operate against a new generation.

Keep a verified copy

If you need the old history, export it before replacing or deleting it. Owner export covers advertised reachable refs, not every unreachable object or historical backup.