queue_rules: - name: default queue_conditions: - check-success ~= ci-app-lint - check-success ~= ci-app-test - check-success ~= ci-app-launch-dev - -check-failure ~= ci-app- - -check-failure ~= ci-slackbot- - -check-failure ~= test-prod-node24 / # Explicitly enumerate sub-checks of test-prod-node24 so that matrix- # job level failures (e.g. `run-playwright (chromium, 2/2, 6.0)`) # reliably block merges. The broader `-check-failure ~= test-prod-node24 /` # has historically let such failures through (observed on run # 24828684287 for PR #11032). - -check-failure ~= test-prod-node24 / build-prod - -check-failure ~= test-prod-node24 / launch-prod - -check-failure ~= test-prod-node24 / run-playwright - -check-failure ~= test-prod-node24 / report-playwright merge_conditions: - check-success ~= ci-app-lint - check-success ~= ci-app-test - check-success ~= ci-app-launch-dev - check-success = test-prod-node24 / build-prod - check-success ~= test-prod-node24 / launch-prod - check-success ~= test-prod-node24 / run-playwright - -check-failure ~= ci-app- - -check-failure ~= ci-slackbot- - -check-failure ~= test-prod-node24 / # Defensive: same explicit enumeration as queue_conditions so the # merge-time gate cannot be bypassed by a matrix-job level failure. - -check-failure ~= test-prod-node24 / build-prod - -check-failure ~= test-prod-node24 / launch-prod - -check-failure ~= test-prod-node24 / run-playwright - -check-failure ~= test-prod-node24 / report-playwright pull_request_rules: - name: Automatic queue to merge conditions: - '#approved-reviews-by >= 1' - '#changes-requested-reviews-by = 0' - '#review-requested = 0' actions: queue: - name: Automatic merge for Preparing next version conditions: - author = github-actions[bot] - label = type/prepare-next-version actions: merge: method: merge