anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: narrow ATVM e2e cypress git drafting rules

Browse Source 
Update the ATVM git instructions so controller-repo git drafting and the SSH-prefixed push example only apply when the operator explicitly asks for the e2e cypress repo or a close variation.

Align AGENTS.md with git-guide.md so generic ATVM git requests no longer assume the controller repo by default.
This commit is contained in:
anthony.wen
2026-04-27 14:54:33 -04:00
parent 96bb156331
commit 22da851f44
2 changed files with 11 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
atvm/git-guide.md
View File

@@ -3,7 +3,10 @@
This file records ATVM-specific git workflow preferences for `/home/aw/code/cds/atvm`.
## Repository Reference
- For ATVM git command drafting, assume the primary operator-managed repo is `/root/cdc-e2e-cyp-12.17.4` unless the operator explicitly says otherwise.
- Do not assume the controller repo by default for every ATVM git request.
- Only switch the default drafted repo to `/root/cdc-e2e-cyp-12.17.4` when the operator explicitly asks for the `e2e cypress` repo or a close variation such as `give me a git for the e2e cypress`.
- When the operator explicitly targets the `e2e cypress` repo, draft the git command itself for that controller repo.
- Do not wrap drafted git commands in an SSH login command to the controller unless the operator explicitly asks for the SSH wrapper too.
## Execution Rule
- For this ATVM workspace, do not automatically perform any git-related command.
@@ -14,7 +17,7 @@ This file records ATVM-specific git workflow preferences for `/home/aw/code/cds/
- Assume the operator will always run ATVM git commands manually.
## SSH Default
- When drafting git commands for the controller repo and SSH-backed git access is needed, use this exact prefix:
- When drafting git commands for the explicitly requested `e2e cypress` controller repo and SSH-backed git access is needed, use this exact prefix:
`GIT_SSH_COMMAND='ssh -i ~/.ssh/id_ed25519_anthony -o IdentitiesOnly=yes'`
- Prefer complete copy-pasteable command sequences that include that prefix for `git fetch`, `git pull`, and `git push` examples when applicable.
@@ -26,6 +29,7 @@ This file records ATVM-specific git workflow preferences for `/home/aw/code/cds/
- The proposed `git commit` command should match the full proposed message, including the detailed body when one is warranted.
- After the proposed commit message, show the exact `git commit` command that would be used.
- Write the proposed ATVM git commands to `/tmp/commit.txt`.
- When drafting a commit for the explicitly requested `e2e cypress` controller repo, present the plain `git add ...` / `git commit ...` command sequence the operator should run after logging into the controller repo, not an SSH-wrapped controller-login command.
- If the operator asks for a git commit, do not commit immediately.
- First show both:
- the proposed commit description/message
@@ -59,7 +63,9 @@ This file records ATVM-specific git workflow preferences for `/home/aw/code/cds/
- draft the exact remote/branch already established in the current ATVM context
- Default generic push form:
`GIT_SSH_COMMAND='ssh -i ~/.ssh/id_ed25519_anthony -o IdentitiesOnly=yes' git push`
- When reminding the operator about the push command after a commit proposal or completed commit, display the SSH-prefixed push command without assuming `origin main` unless that remote/branch was explicitly established.
- When reminding the operator about the push command after a commit proposal or completed commit for the explicitly requested `e2e cypress` controller repo, always display the SSH-prefixed push command without assuming `origin main` unless that remote/branch was explicitly established.
- Every commit draft response for the explicitly requested `e2e cypress` controller repo must include the SSH-prefixed push example.
- Every post-commit response for the explicitly requested `e2e cypress` controller repo must include the SSH-prefixed push example.
- Write the proposed push command to `/tmp/commit.txt`.
## Commit Scope