From ee54a98063efe6dbf800cd911996fae47bf55ab5 Mon Sep 17 00:00:00 2001 From: Richard Zink Date: Thu, 5 Nov 2026 14:50:31 +0100 Subject: [PATCH] Note frequent commits and push-on-deploy in agent rules Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index bc1344a..6577448 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -4,6 +4,7 @@ Always commit and push after every completed, meaningful change in this repository. This keeps changes easy to review and easy to revert. +- Commit often: commit and push right after every completed logical change, not in large batches at the end of a session. - Do not leave finished code changes uncommitted. - One commit should represent one coherent change or one coherent follow-up step. - Do not deploy, rebuild the public version, bump the version, or push deployment changes unless the user explicitly asks for deployment. @@ -93,6 +94,8 @@ When a deployable point is reached, ask the user whether deployment should be pe When asking for deployment approval, briefly explain what changed and what the user should test after deployment, if manual testing is needed. Examples include campaign editor script prompts, custom mission spawn actions, debug overlays, browser/WASM behavior, touch/menu behavior, or multiplayer-related flows when those areas changed. +A deployment always includes a push: the version bump commit (and any other finished commits) must be pushed to `origin main` before or together with the deploy. Never deploy unpushed code. + The usual deployment flow is: ```bash