Push Only After Rebuild

Rule

Before every push: Build first and verify everything works. Only then commit and push.

Flow (always in this order)

1. •

   Rebuild
   From project root:

   bash

   bash scripts/rebuild-and-restart.sh
   

   • •If the build fails: Stop. Inform the user and do not commit or push.
   • •If the build succeeds: Proceed to step 2.
2. •

   Commit (only if there are changes from this chat)
   Only commit changes that were made in this conversation/thread. Do not commit changes from other chats or unrelated uncommitted work.

   bash

   git status
   

   • •If there is nothing to commit: Optionally do step 3 only (push), if there are already commits to push.
   • •If there are changes: Stage only the files you edited in this chat (not git add -A), then commit:
   bash

   git add <path-to-file1> <path-to-file2> ...
   git commit -m "..."
   

   • •If the user explicitly asks to "commit everything" or "commit all changes", then use git add -A and commit.
3. •

   Push

   bash

   git push
   

When to apply

• •User says e.g. "push", "commit and push", "push changes", "deploy to git".
• •User wants to send changes to the remote repo – then always rebuild first.

When to skip

• •User wants to commit only without push → still rebuild first, then only commit (no push).
• •User wants to push only with no new changes (already committed) → only git push; rebuild optional but recommended if code was changed recently.

Scope of commit

• •Default: Stage and commit only files that were modified in this chat/thread. Do not use git add -A so that changes from other chats or sessions are not included.
• •Exception: If the user explicitly asks to commit all changes or everything, then use git add -A.

Summary

Order: Rebuild → (only on success) Commit (if needed) → Push. Never push without a successful build first. Commit scope: Only files changed in this conversation, unless the user asks to commit everything.