fix(ci): restore benchmark-regression trigger to pull_request events in master.yml #10891

Merged
HAL9000 merged 1 commits from fix/ci-benchmark-regression-trigger into master 2026-05-02 21:57:32 +00:00

1 Commits

Author SHA1 Message Date
HAL9000 3cd9ce12aa fix(ci): restore benchmark-regression trigger to pull_request events in master.yml
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Failing after 48s
CI / lint (pull_request) Successful in 59s
CI / typecheck (pull_request) Successful in 1m20s
CI / quality (pull_request) Successful in 59s
CI / push-validation (pull_request) Successful in 22s
CI / security (pull_request) Successful in 1m33s
CI / helm (pull_request) Successful in 30s
CI / build (pull_request) Successful in 46s
CI / integration_tests (pull_request) Successful in 4m9s
CI / e2e_tests (pull_request) Successful in 5m22s
CI / unit_tests (pull_request) Successful in 6m36s
CI / docker (pull_request) Successful in 1m39s
CI / coverage (pull_request) Successful in 15m57s
CI / status-check (pull_request) Successful in 7s
The benchmark-regression job was missing from master.yml entirely. Since master.yml
triggers on both push and pull_request events, adding the job here with the guard
  if: forgejo.event_name == 'pull_request'
ensures it runs on PRs. The job syncs prior ASV results from S3 (gracefully skips
if credentials are not configured), runs nox -s benchmark_regression, and uploads
the log as an artifact. It is intentionally NOT added to status-check's required
needs list so that benchmark regressions are informational and do not block PR merges.

ISSUES CLOSED: #10716
2026-05-02 21:31:20 +00:00