Preflight context
FluxGit surfaces dirty files, branch drift, published branch warnings and conflict risk before a risky operation starts.
FluxGit helps developers slow down only when Git can cost them work: checkout with local changes, discard, reset, rebase, merge, cherry-pick and branch surgery. The goal is not to hide Git. It is to show consequence, safer alternatives and recovery context before the operation runs.
Terminal Git and many visual clients make destructive commands fast. That speed is useful until a dirty worktree, unpublished commit or stale branch turns one click into an hour of recovery. Teams need a Git client with undo-oriented thinking, but honest enough to say when an action is not recoverable by FluxGit.
FluxGit does not promise that every Git operation can be undone. Restore point coverage is expanding for dangerous history workflows. Discard and clean-style operations must still be treated as destructive unless the user stashes, commits or otherwise preserves the work first.
Safety rails combine state inspection, plain-language warnings and recovery-first defaults.
FluxGit surfaces dirty files, branch drift, published branch warnings and conflict risk before a risky operation starts.
When possible, the UI points toward stash, commit, restore point or rescue branch options instead of forcing a destructive path.
Restore points, reflog entries and Safety Timeline surfaces make recent risk events easier to inspect after the fact.
Safety checks are designed around local repository state. Licensing and feedback should not require repository contents, file names, branch names, commit IDs, paths, remotes or diffs by default. AI/provider flows are separate and require their own explicit configuration.