docs(ops): record the 2026-08-12 merge-gate status — throttled, not frozen - #126
Conversation
…rozen The gate reads as frozen (~25h with 16+ CLEAN PRs) but is actually a single-runner throughput queue plus the fleet auto-ship review ladder. Snapshot: 14 CLEAN / 27 BLOCKED / 9 DIRTY PRs, 27 queued CI runs, one busy runner, last merge #122 at 10:59 UTC. The runner CI fix landed 2026-08-11; merges resumed and auto-ship is actively draining the queue. Captures the measured ~2.5-min CI duration, the ladder states (WAITING on two-flagship panels, SKIPPED awaiting flagship review, HELD for Nish authority), and the local-only retention-automation path failure (machine state, not repo content). Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Warning Review limit reached
Next review available in: 26 seconds Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 38c9640162
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | Open PRs | 50 | | ||
| | — `CLEAN` (mergeable now) | 14 | | ||
| | — `BLOCKED` (CI queued/running) | 27 | | ||
| | — `DIRTY` (behind `main`) | 9 | |
There was a problem hiding this comment.
GitHub's mergeStateStatus uses DIRTY for a merge conflict; a merely outdated head is BEHIND. Consequently, these nine PRs are not known to be "just behind," and the later recommendation that they only need a main refresh understates the manual conflict resolution potentially required. Correct the classification so this operational snapshot does not misdiagnose part of the queue.
Useful? React with 👍 / 👎.
| ## What is actually merging the queue | ||
|
|
||
| `auto-ship` (agent-state fleet machinery, not this repo) owns the merge step. It is | ||
| actively working tinystudio-in as of 17:13 UTC: red-tier PRs wait on two-flagship |
There was a problem hiding this comment.
The snapshot was taken at 11:47 UTC and the commit was created at 11:48 UTC, so activity "as of 17:13 UTC" could not have been observed for this diagnostic. Given the nearby 17:17 IST conversion, this appears to mean 17:13 IST (11:43 UTC); correct the timezone or time so the evidence supporting the active-drain conclusion is chronologically valid.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 105a7d7750
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - Nothing merged between 2026-08-10 00:38 IST (#35) and 2026-08-11 08:38 IST (#65): | ||
| the runner CI fix landed 2026-08-11, then merges resumed (#65, #68, #71, #74, #81, | ||
| #84, #111, #122). |
There was a problem hiding this comment.
The repository history contradicts this explanation: PR #47 landed at 2026-08-10 23:07 IST and PR #58 at 2026-08-11 03:01 IST, both between #35 and #65, while #65 itself landed at 14:08 IST rather than 08:38 IST. This makes the asserted uninterrupted freeze and the claim that merges resumed with #65 inaccurate, undermining the document's diagnosis of the reported stall.
Useful? React with 👍 / 👎.
1 participant
What
Adds
docs/merge-gate-status-2026-08-12.md— a snapshot diagnostic of thetinystudio-in merge gate as of 2026-08-12 11:47 UTC.
Why
The backlog item "merge gate frozen ~25h: 16 open PRs all MERGEABLE/CLEAN"
reads as a broken gate. Live investigation shows the gate is throttled, not
frozen:
mainrequiresrepo-checks(strict) on a single self-hosted runner.busy runner, last merge chore(ci): remove nonfunctional CodeQL analyze job #122 at 10:59 UTC.
and each merge re-queues main + deploy runs on the same runner.
auto-shipis actively draining the queue (WAITING on two-flagship panels,SKIPPED awaiting flagship review, HELD for Nish authority) — the review
ladder is the designed gate, not a stall.
repo-checksis green; the only localnpm run cifailureis a machine-local automation path (owned by open retention items / fix(retention): gate must target the git main worktree, not the twin holding main #105),
not repo content.
Verification
npm run cion a fresh clone is green on the runner (repo-checks passes).ghAPI at snapshot time.