From 08b2ab3104ca3ad08ec72e10e9591d7c6e0c6f67 Mon Sep 17 00:00:00 2001 From: "anthony.wen" Date: Fri, 20 Mar 2026 21:31:10 -0400 Subject: [PATCH] Tighten git push guidance to require terminal-only execution Update the git guide so the assistant does not execute git push commands when credentials or SSH key passphrases might be required. Instead, the assistant must show the exact push command and direct the user to run it directly in the terminal. Keep the existing rule that passwords and passphrases must not be accepted through chat and that password handoff requests must be refused. --- git-guide.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/git-guide.md b/git-guide.md index 0e72a01..10dbb65 100644 --- a/git-guide.md +++ b/git-guide.md @@ -16,7 +16,8 @@ This file records repo-specific git workflow preferences for `/home/aw/code/cds` ## Push Requests - When the user asks to push, use `git push -u origin main` by default unless the user explicitly asks for a different remote or branch. -- If `git push -u origin main` or any git command prompts for credentials or an SSH key passphrase, stop at the prompt and tell the user to enter the secret directly in the terminal instead of sending it in chat. +- Do not execute `git push -u origin main` or any other git push command from the assistant when credentials or an SSH key passphrase might be required. +- Instead, show the exact push command and tell the user to run it directly in the terminal. - Do not accept passwords or passphrases through chat for git operations. - If the user asks the assistant to take the password/passphrase handoff, refuse and direct the user to complete the prompt from the terminal.