Document approval gate for git request variants
This commit is contained in:
@@ -62,6 +62,8 @@ This file defines how to operate and maintain the ATVM workspace in `/home/aw/co
|
||||
- Always show exact planned ATVM commands before execution.
|
||||
- Never execute setup or automation commands that require approval until the operator explicitly approves them.
|
||||
- For ATVM run approvals, treat `approve` as run-with-watcher and `approve without watcher` as run-without-watcher.
|
||||
- Treat git/commit requests as a separate approval gate.
|
||||
- Follow `/home/aw/code/cds/git-guide.md` for commit-request handling, including the rule that phrases such as `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`, and close variations are prepare-only until the operator explicitly approves the displayed commit command.
|
||||
- After `cmc-templates.py`, always verify that the generated spec files and the config `specPattern` still include every requested VM before starting `run-sorry-cypress.py`.
|
||||
- If any requested VM is missing after template generation, stop and report the mismatch instead of launching the runner.
|
||||
- When the watcher is requested, start the watcher before `run-sorry-cypress.py`.
|
||||
|
||||
Reference in New Issue
Block a user