Actually run CI on the right versions of Node #2499
Merged
Mergify / Summary
succeeded
Apr 17, 2024 in 0s
2 potential rules
Rule: Automatic merge (squash) on CI success (merge)
-
-closed
[📌 merge requirement] - all of:
-
label=automerge
-
label!=no-automerge
-
status-success=all-web3-checks
- any of:
-
-files~=^packages/library-legacy/
-
status-success="Validate commit message"
-
-
-
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
Rule: Remove automerge label on CI failure (label, comment)
-
#status-failure!=0
-
label=automerge
2 not applicable rules
Rule: Add community label to outside contributions (label)
-
author≠@core-contributors
-
author≠@spl-triage
-
author≠@spl-maintainers
-
author≠@spl-write
-
author≠dependabot[bot]
-
author≠github-actions[bot]
-
author≠mergify[bot]
Rule: Request review of community contributions from community PR subscribers (request_reviews)
-
#approved-reviews-by=0
-
#review-requested=0
-
author≠@core-contributors
-
author≠@spl-triage
-
#changes-requested-reviews-by=0
-
#commented-reviews-by=0
-
author≠@spl-maintainers
-
author≠@spl-write
-
author≠dependabot[bot]
-
author≠github-actions[bot]
-
author≠mergify[bot]
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branch
Additionally, on Mergify dashboard you can:
- look at your merge queues
- generate the Mergify configuration with the config editor.
Finally, you can contact us on https://mergify.com
Loading