Repository navigation
Conversation
Regression specs under tests/e2e never ran on PR CI — only schedule and release called e2e.yml — so a red regression test could merge green. Path-filter and workflow_call the E2E suite when E2E-relevant files change. Closes stablyai#10518
📝 WalkthroughWalkthroughThe pull request workflow now includes an 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Use merge-base diffs so base-branch drift does not false-trigger E2E, fail the detector when git diff cannot compute the PR range, and pin least-privilege contents:read on both the detector and reusable E2E workflow.
Sync update (
|
|
Picked this up in #11131 — thanks @innocarpe, the diagnosis here was right and the path-filter approach is the correct shape. Your two commits are preserved as the base of that branch, rebased onto current
Also added a contract test so neither can regress. Closing this in favor of #11131 — full credit retained via Co-authored-by. |
Summary
pr.ymlnever callede2e.yml, so a PR could add a red regression test and still go green ([Bug]: E2E regression tests can merge red — PR CI never runs the E2E suite #10518).tests/e2e/**,playwright.*, or.github/workflows/e2e.yml,workflow_callthe existing E2E suite.Test plan
src/→ no e2e jobtests/e2e/**→ e2e workflow runsCloses #10518
ELI5
PRs that only touched E2E tests never ran the E2E workflow, so broken tests could look green. Path filters now trigger E2E when test/e2e paths change while leaving ordinary PRs light.