From ba611e848ec0ddbdcbab07b662b940e07cd87c5a Mon Sep 17 00:00:00 2001 From: Julien Cristau Date: Fri, 9 Sep 2022 18:08:56 +0200 Subject: [PATCH] mergify: allow complete-push check as an alternative to complete-pr in queue conditions (#26902) PRs created by github actions don't get a pull-request taskcluster graph scheduled (because that is only done for PRs created by collaborators). However, if the PR is created in the main fenix repo, typically because it comes from one of our internal github workflows, then we get a push graph, which is sufficient to run the required checks. This change lets mergify consider a green `complete-push` task as sufficient to queue a PR (in addition to all the other conditions, e.g. wrt review), which will allow PRs created by the update-nimbus-experiments workflow to be queued by mergify instead of having to be merged by a repo admin. --- .mergify.yml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/.mergify.yml b/.mergify.yml index 23564e676..de81dd583 100644 --- a/.mergify.yml +++ b/.mergify.yml @@ -77,7 +77,9 @@ pull_request_rules: rebase_fallback: none - name: Needs landing - Rebase conditions: - - check-success=complete-pr + - or: + - check-success=complete-pr + - check-success=complete-push - label=pr:needs-landing - "#approved-reviews-by>=1" - -draft @@ -90,7 +92,9 @@ pull_request_rules: rebase_fallback: none - name: Needs landing - Squash conditions: - - check-success=complete-pr + - or: + - check-success=complete-pr + - check-success=complete-push - label=pr:needs-landing-squashed - "#approved-reviews-by>=1" - -draft