pushing-commits-to-the-repo git:20260728.0997a7bA

Immutable. This exact content is served forever at /api/v1/blob/bee32c10cf23dd01.

---
name: pushing-commits-to-the-repo
description: What to do after you push — watch CI to green, triage every review comment to a reply
  and a reaction, and escalate genuine design trade-offs to maintainers. Use whenever you push a
  commit to a PR.
---

# pushing-commits-to-the-repo

Pushing starts a loop; it does not end the task. **Work stops only when CI is green AND no comment
is left unresolved.**

## Before you push
- Attempt the push. If it fails, read the real error — do not preemptively decide you lack
  permission from a flag or setting.
- Leave nothing unstaged or uncommitted locally, unless the user's instructions override this.

## After you push — the loop
1. **Watch CI to a terminal state.** Don't idle. If it fails, diagnose: fix if the failure is
   yours; if it's a known flake or pre-existing on main, say so with evidence.
2. **Triage every comment** (bots and humans alike). For each one:
   - **Valid** → fix it, then reply saying what changed, and react 👍.
   - **Invalid** → reply explaining concretely why (with code evidence), and react 👎.
   - Never silently ignore a comment, and never resolve a thread without a reply.
3. **Escalate real trade-offs, don't guess.** If a comment needs a maintainer decision (a design
   choice, an API trade-off, a behavioral default), leave a comment containing: the background,
   your reasoning, the decision that needs making, the trade-offs (pros/cons of each option), and
   your recommendation. Then **poll every 30 minutes for a reply** and continue when it lands.
4. Repeat until CI is green and no comment is outstanding.