ci(e2e-stand): trigger the stand suite on any backend, frontend or tests change - #2458
ci(e2e-stand): trigger the stand suite on any backend, frontend or tests change#2458ktursunov wants to merge 1 commit into
Conversation
…nd and tests Mirror the changes job's relevance regex as an explicit paths: list on the pull_request trigger, and broaden both in step: any change under tests/, src/backend/ or src/frontend/ (not just tests/stand, tests/lib and the frontend helm chart) now counts as stand-relevant. On pull_request every job still skips, so the filter only prunes no-op runs from the Actions tab; the changes job keeps doing the same filtering for merge_group, which supports no paths: key. While the filter exists, Stand E2E can only be required on merge_group, never at PR level - a required check whose workflow never triggers reports as pending forever. The comments record that constraint. Signed-off-by: Konstantin Tursunov <Konstantin.Tursunov@constructor.tech>
|
Warning Review limit reached
Next review available in: 57 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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 |
1 participant
What
Adds an explicit
paths:filter to thepull_requesttrigger of.github/workflows/e2e-stand.yml, mirroring thechangesjob's relevance regex, and broadens both in the same step:tests/**(wastests/stand/,tests/lib/,tests/pyproject.toml,tests/uv.lock)src/frontend/**(wassrc/frontend/helm/only)src/backend/**(unchanged)deploy/compose/**, seed tool,docker-compose.yml,dev-compose.sh, backendopenapi.jsondocs, this workflow, the trace-redaction scriptWhy
The compose-stand suite must go with any change to the backend, the frontend, or the tests themselves. The previous scope missed frontend source changes and non-stand test changes.
Notes
pull_requestevery job still skips by design, so the new filter only prunes no-op skipped runs from the Actions tab.changesjob keeps doing the same filtering formerge_group(the event supports nopaths:key); the two lists are documented as needing to stay in sync.Stand E2Ecan only be made required onmerge_group, never as a PR-level required check — a required check whose workflow never triggers reports as pending forever and would block queue entry. Verified the current main ruleset requires only "Run E2E suite" and "secrets (diff)", so nothing breaks today; the workflow comments record the constraint.