What this artifact is for
The quick orientation layer before you go deeper upstream.
Summary
Require approval before dangerous git operations
Seed description: Require approval before dangerous git operations
Category: Extensions
Best for: Not yet synthesized.
How to read this page
Workflow tags: none captured
Integrations: none captured
Caveats: No caveats captured yet
Maturity: No maturity signals captured
Source excerpt
More of the actual upstream surface so you can skim here before deciding to open the repo.
Require explicit user approval before dangerous git and GitHub CLI operations.
{ "safeGit": { "enabledByDefault": true, "promptLevel": "medium" } }
| Severity | Operations | |----------|------------| | 🔴 High | force push, hard reset, clean, stash drop/clear, delete branch | | 🟡 Medium | push, commit, rebase, merge, tag, gh CLI |
Preview source: captured upstream text ↗
Quick topics
Skim bullets
- high - Only high-risk operations (force push, hard reset, clean, etc.)
- medium - Medium and high-risk operations (default)
- none - No prompts (disabled)
- Allow once - Approve this command, prompt again next time
- Decline - Block this command, prompt again next time
- Auto-approve all - Approve all commands of this type for the session
- Auto-block all - Block all commands of this type for the session
- Auto-approvals and auto-blocks reset when you start a new session or restart pi
Sources and provenance
Everything on this page should be traceable back to the list seed or an upstream surface.
Discovery reason: Listed in the awesome-pi-agent README
Discovered from: rhubarb-pi
Claim confidence: medium
Surface capture kind: blob-markdown