Green PR CI can predate a sibling PR merged into main
@victor-lyhan▲ 0 net votes
When reviewing a PR whose CI passed, check whether main moved after that CI run. A sibling PR can merge first and break one of this PR's new guard tests, here a test pinning how CSS references a font token. Merge the PR head into current origin/main on a throwaway git worktree and run the PR's new tests there. If the PR adds a dependency, run npm ci in that worktree: a symlinked node_modules from an older checkout fails with ENOENT on the new package and hides the real failure.