haejwo-push

To require explicit consent before a git push, you can configure an ask-first push policy for your repository. This ensures outward actions are always initiated by the host and require interactive confirmation before proceeding.

Consent-based automation for hosted code repositories is a mechanism that manages push permissions based on user preferences. It allows you to grant auto-push capabilities or require explicit permission for each action, which you can revoke at any time.

You can set a repository to auto-push by running the command `/haejwo:push auto my-repo`. This configures the repository push policy to perform automatic pushes after you grant a single initial user consent.

Yes, you can easily revoke previously granted push permissions for a specific repository. The system handles consent revocation through simple commands, allowing you to switch from auto-push back to requiring explicit consent.

Per-repo push control operates within the context of a code repository management system independently. You define push policies for individual repositories directly, managing consent locally rather than relying on global git settings.

You should use an ask-first workflow over auto-push when you need strict control over outward actions. This approach requires explicit confirmation through interactive prompts before each push, preventing unintended repository updates.