docs(agent): health audit — integrations-and-migrations-1 - #12751
Merged
mergify[bot] merged 1 commit intoSep 9, 2026
Merged
Conversation
mergify-ci-bot
force-pushed
the
docs-agent/health-audit-integrations-and-migrations-1
branch
from
September 9, 2026 10:33
302b23d to
75bcdf5
Compare
Contributor
Merge Protections🟠 1 of 6 protections blocking · waiting on 🤖 CI
🟠 🤖 Continuous IntegrationWaiting for
Waiting checks:
|
sileht
approved these changes
Sep 9, 2026
sileht
approved these changes
Sep 9, 2026
jd
approved these changes
Sep 9, 2026
Contributor
Merge Queue Status
This pull request spent 6 minutes 10 seconds in the queue, including 2 minutes 48 seconds running CI. Required conditions to merge
|
63 tasks
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
integrations/gha.mdx— the caution above the Monorepo CI example said thescopesaction "requires a pull request context" and that apushtriggercauses failures. The repository's own production deploy workflow runs
action: scopesonpushandworkflow_dispatchwith no pull-request guard,passing an explicit
base; its inline comment states the action diffsbase...HEADvia local git and that the scopes-to-API upload is a no-op withno pull request.
baseis a declared input of the action (per the answeredgha-mergify-ci-flaky-test-detection-inputinput list) and was added in v22;the docs pin
v25viasrc/data/gha-mergify-ci-version.json, so it isavailable. Rewrote the caution to name the real mechanism and keep the
if:guard as one of two valid answers.
integrations/gha.mdx— the example passed notokento thescopesaction,so the detected scopes never reach Mergify and the Merge Queue Scopes the same
section advertises never see them. Both real
action: scopesinvocations inthe monorepo pass
token: ${{ secrets.MERGIFY_TOKEN }}; the oneaction: wait-jobsinvocation deliberately does not, which is the control.merge-queue/scopes/others.mdx:79also passes it. Added the input plus aparagraph explaining what the token buys, that
wait-jobsneeds none, and theDependabot-secrets consequence. Both gha edits ship as one finding,
gha-scopes-token-input-and-event-context, because both are the same exampleand I read "every page named by exactly one finding" as binding.
…truncated; the rest is in the run log.