atvm: stop assuming origin main in push guidance
Update the ATVM git guide so push examples do not hardcode origin/main. Prefer the operator-specified remote and branch when provided, and otherwise draft a generic SSH-prefixed git push command or use the remote/branch already established in context.
This commit is contained in:
@@ -52,9 +52,14 @@ This file records ATVM-specific git workflow preferences for `/home/aw/code/cds/
|
||||
## Push Requests
|
||||
- For this workspace, never execute `git push` from the assistant.
|
||||
- When the operator asks to push, show the exact push command only.
|
||||
- Default push command:
|
||||
`GIT_SSH_COMMAND='ssh -i ~/.ssh/id_ed25519_anthony -o IdentitiesOnly=yes' git push origin main`
|
||||
- When reminding the operator about the push command after a commit proposal or completed commit, display that full SSH-prefixed command unless they explicitly ask for a different remote, branch, or SSH pattern.
|
||||
- Do not hardcode `origin main` in this ATVM-local guide.
|
||||
- When drafting a push command, use the operator's requested remote/branch if provided.
|
||||
- If the operator does not specify the remote/branch, either:
|
||||
- draft a generic SSH-prefixed `git push` command, or
|
||||
- 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.
|
||||
- Write the proposed push command to `/tmp/commit.txt`.
|
||||
|
||||
## Commit Scope
|
||||
|
||||
Reference in New Issue
Block a user