Update the git guide so credential and passphrase prompts are never handled through chat. Document that when git push -u origin main or any git command prompts for a secret, the assistant must stop and direct the user to enter it directly in the terminal. Also document that the assistant must refuse requests to take password or passphrase handoff for git operations.
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. - If
git push -u origin mainor 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 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.