docs: close gaps found by docs-gap-analysis#11996
Open
Conversation
Member
Author
|
This pull request is part of a Mergify stack:
|
Contributor
Merge Protections🔴 2 of 7 protections blocking · waiting on 👀 reviews
🔴 👀 Review RequirementsWaiting for
This rule is failing.
🔴 🔎 ReviewsWaiting for
This rule is failing.
Show 5 satisfied protections🟢 ⛓️ Depends-On RequirementsRequirement based on the presence of
🟢 🤖 Continuous Integration
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
Corrections surfaced by the new docs-gap-analysis skill against the last
90 days of changelog entries:
- configuration/conditions.mdx: document `{{ author }}` as a built-in
condition value, and add prose for the `check-cancelled` and `scope`
condition attributes (previously only rendered in the generated table)
- ci-insights/auto-retry.mdx: rules are now scoped per repository via the
repository selector (the per-rule `repository` condition is no longer
needed); mention the "Test your log patterns" tester in the rule builder
- merge-queue/github-rulesets.mdx: document that Mergify honors GitHub's
"Require approval of the most recent push" by auto-injecting the matching
condition
- merge-queue/scopes.mdx: fix broken cross-link
(/merge-queue/parallel-scopes -> /merge-queue/queue-modes#limiting-concurrency-per-scope)
Verified with the proofread pipeline (style/technical/structure/consistency)
and `pnpm check` (0 errors). The stale `allow_checks_interruption` default in
merge-queue/priority.mdx is intentionally NOT changed: the schema still says
default true while the changelog says false, so it needs product confirmation.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I57ed4284abe888c205fbbb07953d7d76d8e335b1
jd
force-pushed
the
devs/jd/worktree-skill/add-docs-authoring-maintenance-skills--e17e7c54
branch
from
b30cb9a to
c8189f5
Compare
jd
force-pushed
the
devs/jd/worktree-skill/close-gaps-found-docs-gap-analysis--57ed4284
branch
from
5979274 to
5c5f5ef
Compare
Member
Author
Revision history
|
JulianMaurin
approved these changes
Jun 30, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Corrections surfaced by the new docs-gap-analysis skill against the last
90 days of changelog entries:
{{ author }}as a built-incondition value, and add prose for the
check-cancelledandscopecondition attributes (previously only rendered in the generated table)
repository selector (the per-rule
repositorycondition is no longerneeded); mention the "Test your log patterns" tester in the rule builder
"Require approval of the most recent push" by auto-injecting the matching
condition
(/merge-queue/parallel-scopes -> /merge-queue/queue-modes#limiting-concurrency-per-scope)
Verified with the proofread pipeline (style/technical/structure/consistency)
and
pnpm check(0 errors). The staleallow_checks_interruptiondefault inmerge-queue/priority.mdx is intentionally NOT changed: the schema still says
default true while the changelog says false, so it needs product confirmation.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com
Depends-On: #11975