safe-git-guard

Prevent destructive git operations by requiring a backup before action. You must create a stash, tag, or branch before running commands like git reset --hard or git clean, ensuring your work is safely recoverable.

The best way to block git push --force on main or master is to enforce No-Touch Zones. This mechanism blocks or warns on force pushes to critical branches in both local and CI workflows, requiring explicit confirmation.

Back up your working directory before a destructive git rebase by running git stash push -m "backup-before-destructive-<date>". This creates a recovery point before the destructive operation begins and prompts you to confirm intent.

Yes, you can enforce git safety and confirmation prompts in CI workflows. The backup-before-action workflow and No-Touch Zones apply across both local and CI environments, blocking destructive commands like git clean -fd and requiring explicit confirmation.

You need a backup before running destructive git commands whenever executing git reset --hard, git push --force on main/master, git clean -fd, or rebase. The backup-before-action workflow requires a stash, tag, or branch to protect critical code from irreversible loss.