Repository navigation
Trim the review cards' boilerplate - #21920
Conversation
Author card:
- Drop the collapsed "How to answer" fold when nothing blocks merge. It
opened "Every 🚨 and ❓ item above needs one of these" on cards that
had none. It comes back if a finding reopens.
- Shorter IMPORTANT/NOTE callouts, browser hint, v3 style caption, and
closing line.
Reviewer's guide:
- The footer is one line: how to push back with #update-review. The rest
("the minutes that matter", where the author's items live) repeated
the TIP callout and the Waiting-on-the-author block.
- Shorter TIP callout, Waiting-on-the-author lead-in, and hand-off line.
- An empty editorial-stances list renders nothing instead of a heading,
caption, and "None" under a line saying stances "still need a human
eye". The v2 monolith keeps its explicit-empty form and long captions
(its golden output is pinned).
Both refresh lanes now re-stamp both cards' footers from the templates
(build-evidence.restamp_footer). Before, a card kept whatever footer it
was first published with, so pre-fold cards like #21760 kept an
expanded "### How to answer" through every refresh.
Compat sweep over the 31 open PRs with v3 cards: 0 new validator
violations on as-is, no-op, and real refreshes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GKHS8qr1o8N7QkAdtHyWPz
Sentinel — merge gate status (preview)Warning
|
| Gate | What it needs | |
|---|---|---|
| ✅ | G1 review-ran | Nothing to do: review current at 3a6b06f7d. |
| ✅ | G2 findings-answered | Nothing to do: every finding answered. |
| 🔴 | G3 right-approver | Needs approval from a member of any review team (pulumi/docs-blog-review, pulumi/docs-guild, pulumi/docs-marketing-review, pulumi/docs-tools) or a repository administrator — no qualifying human approval at this head (bot approvals never count). |
| ➖ | G4 infra-evidence | Doesn't apply to this PR: no changed path affects the deploy. |
| ➖ | G5 oversized-ack | Doesn't apply to this PR: not oversized. |
Break glass: a member of a routing team (.github/review-routing.yml teams:) can apply review:waived, which is logged.
Evaluated at head 3a6b06f7d.
A refresh already rewrote the author card's callout and both footers; the guide's TIP callout was the one piece of fixed text an old card kept through every refresh. apply-update now swaps it for the composer's current one (build-evidence.restamp_brief_orient). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GKHS8qr1o8N7QkAdtHyWPz
|
🤖 Review errored. Flip to draft and back to ready, or mention |
|
Your site preview for commit 3a6b06f is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-21920-3a6b06f7.s3-website.us-west-2.amazonaws.com |
The v3 self-check refuses drafts that carry v2 section names like "⚠️ Low-confidence", to catch composer scaffolding that wasn't rewritten. It scanned the whole draft, including text quoted from the PR. This PR edits output-format.md, whose changed line mentions "⚠️ Low-confidence"; the extractor listed it as an editorial stance, the stance bullet quoted it, the self-check failed, and the review errored (run 36204219422). Any PR that edits the review docs could hit the same thing. Quoted text always renders through quote() inside *"…"*, so the check now strips those spans first. Reproduced with that stance: CAUTION banner before the fix, none after. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GKHS8qr1o8N7QkAdtHyWPz
|
@claude #new-review (The first review errored on a composer self-check that tripped on text quoted from this PR's own diff. Fixed in 3a6b06f.) Generated by Claude Code |
|
@claude #new-review (Retry: the previous request was cancelled by the triage run from the same push, which then skipped.) Generated by Claude Code |
Reviewer's guide v1 — not for the authorTip Check the PR author: nothing here is yours. Your to-do list is the "Author action guide" comment. Approval needed from: @pulumi/docs-tools — any member's approval satisfies the merge gate. Note What this PR changes:
The risk is a composer or evidence-builder change that drops or misrenders a finding on the published cards. The claim pipeline and the infra-domain read of the changed scripts ran; tests weren't run in this review. Review confidence:
|
Author action guide v1 — nothing blocks mergeNote Nothing here needs an answer from you. A human reviewer still approves the merge. This PR trims boilerplate from the v3 review cards (footers, composer and evidence-page output, style-suggestion posting) and updates tests and fixtures; the review checked the changed scripts, reference docs, and the one factual claim. Full evidence: verification trail, investigation log, review history. Review v1 · updated 2026-09-26T00:44:23Z · head commit 3a6b06f Please don't edit or delete this comment; it's the review's record. |
Proposed changes
Follow-up to #21908. It cuts fixed text on both review cards that repeated something else on the card, or said nothing.
Author card
#update-reviewtag doesn't count" stays in the always-visible callout.Reviewer's guide
@claude <your point> #update-reviewand the review re-checks with your input." The rest ("theOld cards pick this up on their next refresh. Both refresh lanes now re-write both cards' footers from the templates. Before this, a card kept whatever footer it was first published with, so cards from before #21908, like #21760's, kept the fully expanded "### How to answer" through every refresh. The rest of the fixed text follows on the next refresh the same way.
The v2 monolith (pre-v3 PRs) keeps its long style caption and its explicit-empty stances block, because its output is pinned byte-identical by
test_v2_golden_unchanged.Testing
make test-review-pipelinepasses. New tests cover:🤖 Generated with Claude Code
https://claude.ai/code/session_01GKHS8qr1o8N7QkAdtHyWPz
Generated by Claude Code