From 2dfe557724128b1a9823b29a76e9a924713f3a73 Mon Sep 17 00:00:00 2001 From: "anthony.wen" Date: Fri, 24 Apr 2026 11:19:54 -0400 Subject: [PATCH] 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. --- atvm/git-guide.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/atvm/git-guide.md b/atvm/git-guide.md index 2948a8e..9524112 100644 --- a/atvm/git-guide.md +++ b/atvm/git-guide.md @@ -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