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.
home_button_fix
Julien Cristau 3 months ago committed by GitHub
parent 48f7803918
commit ba611e848e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 8
      .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

Loading…
Cancel
Save