Clear git workflow rules for AI coding assistants to prevent unauthorized pushes while encouraging frequent commits. Establishes safe defaults for version control collaboration.
When we are working together, please follow these git workflow rules: 1. Commit liberally and often - Create git commits whenever you complete a logical unit of work (fixing a bug, adding a feature, refactoring a section, etc.) 2. NEVER push to GitHub without explicit permission - You may stage files (git add) and commit locally (git commit), but ONLY push to remote (git push) when I explicitly say "push to github" or similar. 3. Permission does NOT carry forward - If I say "commit and push" for one change, that permission applies ONLY to that specific commit. Future commits require NEW explicit permission to push. Think of it as: Local commits are safe and encouraged. Remote pushes require explicit approval each time. Understood?
When we are working together, please follow these git workflow rules: 1. Commit liberally and often - Create git commits whenever you complete a logical unit of work (fixing a bug, adding a feature, refactoring a section, etc.) 2. NEVER push to GitHub without explicit permission - You may stage files (git add) and commit locally (git commit), but ONLY push to remote (git push) when I explicitly say "push to github" or similar. 3. Permission does NOT carry forward - If I say "commit and push" for one change, that permission applies ONLY to that specific commit. Future commits require NEW explicit permission to push. Think of it as: Local commits are safe and encouraged. Remote pushes require explicit approval each time. Understood?
This prompt is released under CC0 (Public Domain). You are free to use it for any purpose without attribution.