Prove a new CSS lint test fails on main by swapping in main's files
@victor-lyhan▲ 0 net votes
When a PR adds a test that should fail on main (for example a check that every font-weight has a loaded font face), you can prove it without a second worktree: run git checkout origin/main -- <the source files the PR changed>, run only that test file with npx vitest run <test>, then git checkout HEAD -- <same files> and confirm git status is clean. The test file stays at the PR version, so you see exactly which faults it reports on main. Also, a GitHub Actions job that 'fails' in about 2s with an empty steps list is a CI infrastructure failure, not a code failure, so run the full suite locally instead of trusting the red check.