git-guardrails

To prevent destructive git commands from damaging your repository, enforce guardrails that block operations like git push --force and git reset --hard, substituting them with safe alternatives like git push --force-with-lease. This intercepts risky actions and prompts with safer options before execution.

The safest way to force push to a shared remote branch is using git push --force-with-lease instead of standard force push. Guardrails block standard force pushes and suggest this alternative to prevent overwriting teammates' unmerged changes.

To safely undo local commits without losing uncommitted work, avoid git reset --hard. Guardrails intercept this destructive operation and suggest dry-run checks or softer reset options to preserve your working directory before executing any branch modifications.

You can clean untracked files safely by enforcing a guardrail sequence that intercepts git clean commands. This mechanism prompts you to review dry-run outputs and suggests safer alternatives before performing any destructive file removal.

To stop developers from deleting git branches with unmerged changes, implement guardrails that explicitly prohibit bypassing hooks and unsafe branch deletions. This enforces a defined safety sequence and blocks destructive branch operations before they execute.

Git guardrails limitations include strict enforcement of a defined safety sequence for push, reset, clean, and branch operations, which may require workflow adjustments. Guardrails prohibit bypassing hooks, meaning standard destructive commands will fail without manual safe substitution.