checkpointbeta
Automatic before covered ops
A restore point is created before covered dangerous operations so you have a way back.
recovery checkpoints
Restore points before history gets dangerous.
Flux restore points create recovery-oriented checkpoints around risky history operations so rebase, reset, cherry-pick and merge feel less like a leap of faith.
The problem: rebase and reset are easy to start, hard to take back.
Dangerous history operations can move HEAD, rewrite commits or discard work in a way that is intimidating to reverse. Without a checkpoint, recovery means digging through reflog by hand under pressure.
Honest beta limit
Flux restore points cover dangerous history operations like reset, rebase, cherry-pick, revert and merge. They are not a universal undo: discard and clean do not create a Flux restore point today, so treat those as destructive unless you stash or commit first.
How FluxGit helps.
undo/redobeta
Expanding coverage
Undo/redo coverage spans covered history operations and is expanding across more flows.
visiblebeta
Shown in the timeline
Restore points appear in the Safety Timeline alongside reflog movement and risk events.
Privacy and security posture.
Restore points are local-first. They reference your own repository state and are never sent anywhere by FluxGit.
Related features.
- Reflog recovery turns local HEAD movement into visible rescue actions.
- Safety rails warn before destructive operations.
- Trinity keeps conflict resolution reviewable.