Repository navigation
chore: land 1 reviewed pull request (batch 69) - #12962
Conversation
…ry shots, removed stories From main's canonical capture at ddab5b7. Every shot that moved more than 1% traces to a merged change; 24 shots join for new or newly planned stories and 10 leave with stories no longer in the plan.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
AI review status for this pull request.
|
|
/approve-spec 5681351 |
There was a problem hiding this comment.
Approved pending CI: CI has not finished on this head yet.
This lands #12961's refresh of the stable visual baseline, which is test data only, and the head's shots reproduce its stated counts (233 changed, 24 added, 10 removed), with every shot that moved more than 1% inside the groups it traces to merged changes.
- After merge, expect shots that render parts restyled on
mainafter the capture (new probe targets for Banner, Pagination and Table states, and a darker placeholder fallback inreset.css) to still show as changed in the visual check until the next refresh.
Claims and files checked
Review mode: full; reason: no-earlier-review
- Claims:
- The batch merges the test-data-only pull request onto current
mainas a merge commit: verified; the head merges main's tip with #12961's head and adds no change of its own. - Nothing else in the batch touches
.github/visual-baseline: verified; #12961 is the only member, and every changed file is under that directory. - The baseline is refreshed from main's capture with
gate.mjs accept --keys all --prune: verified; the manifest's new decision promotes all 530 shots and prunes 10 from a successful CI capture dispatched onmain. - 233 shots changed, 24 were added and 10 were removed: verified with the gate's own comparison settings; 261 files change because
--keys allalso rewrites 28 shots that moved under the gate's threshold. - Every shot that moved more than 1% traces to a merged change that #12961 lists: verified; the 38 such shots fall exactly into its 12 groups, and every cited change is in main's history before the capture.
- Scope is baseline test data only, with no records: verified; 295 PNGs and the manifest change, and no record does.
- The member pull request is closed with a note once this merges: not checkable at this head, since it is a post-merge step.
- The batch merges the test-data-only pull request onto current
- Files:
.github/visual-baseline/manifest.json: clear..github/visual-baseline/shots/*.png(261 modified, 24 added, 10 deleted): clear; every head file is a well-formed PNG that matches its manifest hash.
PR Analysis Report🔎 Preview ·
|
Merges this test-data-only pull request onto current main as a merge commit. Nothing else in this batch touches
.github/visual-baseline.The visual baseline is refreshed from main's capture with
gate.mjs accept --keys all --prune: 233 shots changed, 24 added and 10 removed. Every shot that moved more than 1% traces to a merged change; the member's description lists them.Scope
Tests:
.github/visual-baseline/(test data only)Records
None.
Writing rubric results
No record changes, so R1–R7 do not apply.
When this merges, the pull request above is closed with a note that names this one.