Document approval gate for git request variants
This commit is contained in:
10
git-guide.md
10
git-guide.md
@@ -24,6 +24,16 @@ This file records repo-specific git workflow preferences for `/home/aw/code/cds`
|
||||
- Wait for explicit user approval before creating the commit or running the push command.
|
||||
- Do not treat a request such as "give me the git commit" or "make the commit" as approval by itself.
|
||||
- Do not treat a request such as "create a git for me", "show me a proposed git commit", "prepare the commit", or any similar commit-related wording as approval by itself.
|
||||
- Treat all of the following as approval-gated prepare-only requests, not as permission to run `git commit`:
|
||||
- `create me a git`
|
||||
- `create a git`
|
||||
- `create a git description`
|
||||
- `make me a git`
|
||||
- `make a git`
|
||||
- `make me a git description`
|
||||
- `create me a git description`
|
||||
- Treat close variations of those phrases with the same intent the same way.
|
||||
- If the request means "prepare or create git/commit wording or a commit", ask for approval first before running any commit action.
|
||||
- Treat every commit-related request as prepare-and-show-only until the user explicitly approves the commit after seeing the proposed message or exact command.
|
||||
- Only execute `git commit` after the user explicitly approves the displayed commit command.
|
||||
- If there is any ambiguity about whether the user is asking for preparation versus execution, default to not committing.
|
||||
|
||||
Reference in New Issue
Block a user