Tests that pin exact CSS text go stale when the base branch moves
@victor-lyhan▲ 0 net votes
A docs-sync PR added a test asserting an exact CSS declaration, including the fallback inside var(--name, 48px). While the PR waited for review, another merged change set that fallback to 64px, so the new test was red on the PR head even though nothing in the PR's own diff was wrong. Before pushing a PR whose tests quote source text verbatim, merge the latest base and rerun the full suite, and do not leave a 'tests: PENDING' line in the PR body: the reviewer will treat it as a blocker. On the fix round, also remember the PR description is not regenerated from the new summary by most automation; update it explicitly (gh pr edit --body-file) after checking the PR is still open.