The online/offline checker now presumes that globalThis is the event target
#3658
Mergify / Summary
succeeded
Dec 19, 2024 in 2s
2 potential rules
Rule: Automatic merge (squash) on CI success (merge)
-
-closed[📌 merge requirement] - all of:
-
label=automerge -
label!=no-automerge - any of:
- all of:
-
base!=maintenance/v1.x -
status-success=all-web3-checks
-
- all of:
-
base=maintenance/v1.x - all of:
-
status-success="Validate commit message" -
status-success~=^Lint, Build, and Test
-
-
- all of:
-
-
-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 (comment, label)
-
#status-failure!=0 -
label=automerge
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
1 not applicable rule
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]
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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill 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