fix: issue when module runned by deno or bun #50
Merged
Mergify / Summary
succeeded
Oct 12, 2024 in 0s
3 potential rules
Rule: automatic merge (merge)
-
-closed[📌 merge requirement] - all of:
-
#check-failure=0 -
#check-pending=0 -
-label~=^acceptance-tests-needed|not-ready -
base=main -
linear-history
-
- all of:
-
#approved-reviews-by>=2 -
#changes-requested-reviews-by=0 -
#review-requested=0
-
-
#commits-behind = 0[🛡 GitHub branch protection] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
Rule: automatic merge on special label (merge)
-
-closed[📌 merge requirement] - all of:
-
#check-failure=0 -
#check-pending=0 -
-label~=^acceptance-tests-needed|not-ready -
base=main -
linear-history
-
- all of:
-
label=merge-fast -
base=main
-
-
#commits-behind = 0[🛡 GitHub branch protection] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
Rule: ask to resolve conflict (comment)
-
conflict
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
2 not applicable rules
Rule: automatic merge for dependabot updates (merge)
-
-closed[📌 merge requirement] - all of:
-
#check-failure=0 -
#check-pending=0 -
-label~=^acceptance-tests-needed|not-ready -
base=main -
linear-history
-
- all of:
-
author=dependabot[bot] -
label=waited -
base=main
-
-
#commits-behind = 0[🛡 GitHub branch protection] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
Rule: Wait for 1 day before validating merge (label)
- all of:
-
author=dependabot[bot] -
updated-at<1 days ago
-
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