anthony.wen
08b2ab3104
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.
1.6 KiB
1.6 KiB
Git Guide
This file records repo-specific git workflow preferences for /home/aw/code/cds.
Repository Reference
- Active repository:
https://git.devreser.com/anthony.wen/cds-ai.git - Treat this repository URL as the current
originfor this workspace unless the user explicitly says it changed.
Commit Message Requests
- If the user asks for a git commit description, draft the proposed commit message first.
- After the proposed commit message, show the exact
git commitcommand that would be used. - After the
git commitcommand, show the exactgit push -u origin maincommand that would be used. - Do not run
git commitimmediately after drafting the message. - Do not run
git pushimmediately after drafting the message. - Wait for explicit user approval before creating the commit or running the push command.
Push Requests
- When the user asks to push, use
git push -u origin mainby default unless the user explicitly asks for a different remote or branch. - Do not execute
git push -u origin mainor 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.
Commit Scope
- When committing, include only the files relevant to the approved change.
- Leave unrelated worktree changes uncommitted unless the user explicitly asks to include them.