This repository was archived by the owner on Oct 26, 2026. It is now read-only.
Repository navigation
ci(dependabot-auto-merge): turn the job off until the objectstack cutover (objectui#13497) - #13527
Merged
Merged
Conversation
…over (objectui#13497) The job's last step enqueues a Dependabot pull request with `gh pr merge --auto` under GITHUB_TOKEN. GitHub starts no workflow run for an event GITHUB_TOKEN caused, so that merge group never gets its `merge_group` runs and holds the head of the queue until the check timeout removes it; every Dependabot force-push re-enqueued it and the stall repeated. The triage ruling on objectui#13497 took the cheaper fix for a repository that is archived at the objectstack-ai/objectstack#25677 cutover: stop enqueuing Dependabot pull requests from Actions. The whole job is off (`if: false`), not only its enqueue step, because the gate that would remain holds a runner per Dependabot rebase only to approve a pull request nothing enqueues. No App or PAT secret is added, the queue timeout is unchanged and no required check is dropped. The header says how to turn it back on. Part of objectstack-ai/objectstack#25677 Claude-Session: https://claude.ai/code/session_01DqwYJmM7nGqhoj84ZUJ9Cz Co-authored-by: Claude <noreply@anthropic.com>
Contributor
Author
|
Dispatch seat record. ACCEPTed on card #13497 (takeover under the maintainer's 2-hour no-progress rule). Generated by Claude Code |
os-zhuang
approved these changes
Oct 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Tesla · project thread
Fixes #13497
Part of objectstack-ai/objectstack#25677
Clause-②: no
Metadata-protocol: none
⛔ Governed surface (
.github/workflows/**, Tier H). This PR stays a draft until an APPROVED review from an authorized approver (os-zhuang or hotlong) is on record; the merge-queue leg of the Governed Surface Queue Guard refuses it otherwise. No agent seat approves it; the dispatch seat lands it after the approval.维护者速读(草稿)
dependabot-auto-merge.yml的唯一 job 关掉(if: false),只改这一个文件,文件头写明原因和怎么恢复。github.actor == 'dependabot[bot]'(文件头写了),或者 revert 这个 PR。What changes
One file,
.github/workflows/dependabot-auto-merge.yml:dependabotjob's condition becomesif: false, with a one-line pointer to the header.github.actor == 'dependabot[bot]', and fix the GITHUB_TOKEN enqueue first).Why
The job's last step enqueues with
gh pr merge --auto --squash --match-head-commitunderGITHUB_TOKEN. GitHub starts no workflow run for an event thatGITHUB_TOKENcaused, so the merge group gets nomerge_groupruns, its required checks never report, and it holds the head of the queue until the check timeout removes it. The card's measurements (the third removal, still pending when the card was filed, is read from #13438's timeline):added_to_merge_queue, bygithub-actions[bot])removed_from_merge_queue)A fourth cycle was live while this PR was written: Dependabot force-pushed #13438 at 10:40:58Z,
github-actions[bot]enqueued it at 10:54:47Z, and at 11:55Z its merge group (gh-readonly-queue/main/pr-13438-…, head6523401e4b) had 0 workflow runs, while the group right behind it (#13515, enqueued by the fleet App) had 5 of 5 runs atsuccess, waiting.The triage ruling on #13497 (comment 6393154205) chose the cheaper of the card's two ways, because this repository is archived at the objectstack-ai/objectstack#25677 cutover: stop enqueuing Dependabot pull requests from Actions, by dropping the enqueue step or disabling the workflow until cutover. ⛔ No App or PAT secret, no shorter queue timeout, no dropped required checks.
Why the whole job, not just the enqueue step
Both forms were measured against the tests that read this workflow:
scripts/__tests__/dependabot-merge-gate.test.tsgh pr mergethat is not behind a green gate" (its anti-vacuity count reads 0) and "runs the gate script and tells it which SHA to judge" (no--match-head-commitleft)if: falseon the job (this PR)Dropping only the step would mean rewriting those two pins as well. It would also keep the gate running on every Dependabot rebase in the cutover window: one runner polling for up to 40 minutes, only to approve a pull request that nothing enqueues. With the job off, the workflow stays as it is, and the tests that pin it don't change.
Verification (local, head
b3d92a46a4)node scripts/check-governed-queue-guard.mjs --test .github/workflows/dependabot-auto-merge.yml.github/workflows/**x1), as expectednode scripts/check-changeset-presence.mjscheck-control-bytes,check-action-ref-convention,check-pre-install-import-graph(--self-testand run),check-shell-escape-residue,check-governed-queue-guard --self-test,check-required-check-set --self-test,check-bash32-floor,check-new-cross-file-line-citations,check-doc-linksscripts/__tests__files that name this workflowscripts/__tests__(underos-verify-lock)Test timed out in 15000msin files that do not read this workflow (check-i18n-dead-keys,check-vi-mock-inherit,dollar-dialect-alias-census); the same three files re-run alone on this head: 0 (259 tests)ifis the booleanfalse; 10 steps, unchangedWhat can't be tested on this PR: the workflow triggers only on a Dependabot pull request, so this PR can't run the changed job. The check comes after the merge: the next Dependabot force-push should produce a skipped
dependabotjob and noadded_to_merge_queueevent.Acceptance notes
Prose elsewhere still says this workflow approves and enqueues:
content/docs/guide/ci-cd-pipeline.md(workflow table row and the "Dependabot Auto-Merge" section),AGENTS.md(the governed-surface list and the merge-queue paragraph), thedependabot-auto-merge.ymlreason inscripts/check-action-ref-convention.mjs, and header comments inscripts/dependabot-merge-gate.mjsandscripts/check-governed-queue-guard.mjs. Not changed here: the card's scope is the workflow, and the repository is archived at cutover. These are reported to the dispatch seat.Fixing this doesn't clear the current queue head. The chore(deps): Bump next from 16.3.8 to 16.4.1 #13438 entry enqueued at 10:54:47Z stays until its timeout, or until a maintainer removes it from the queue.
Adds no product-specific widget, dialog, hook or string (see AGENTS.md › Product-neutral renderer)
🤖 Generated with Claude Code
Session:
https://claude.ai/code/session_01DqwYJmM7nGqhoj84ZUJ9Cz