Skip to content

feat(zoe): zoe part of minimal want patterns using M.containerHas(el,n) #10952

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: markm-want-patterns-only-ertp
Choose a base branch
from

feat(zoe): zoe part of minimal want patterns using M.containerHas(el,n)

9b970c3
Select commit
Loading
Failed to load commit list.
Draft

feat(zoe): zoe part of minimal want patterns using M.containerHas(el,n) #10952

feat(zoe): zoe part of minimal want patterns using M.containerHas(el,n)
9b970c3
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jul 21, 2025 in 2s

no rules match, no planned actions

4 not applicable rules

Rule: merge to master (queue)

  • -draft [📌 queue requirement]
  • base=master
  • label=automerge:no-update
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue merge]
      • base=master
      • any of:
        • check-pending=integration-test-result
        • check-success=integration-test-result
        • label=bypass:integration
      • check-success=breakage
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • any of:
    • #commits-behind=0
    • label=bypass:linear-history
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: rebase updates then merge to master (queue)

  • -draft [📌 queue requirement]
  • base=master
  • label=automerge:rebase
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue rebase]
      • base=master
      • any of:
        • check-pending=integration-test-result
        • check-success=integration-test-result
        • label=bypass:integration
      • check-success=breakage
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • any of:
    • linear-history
    • #commits-behind>0
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: squash to master (queue)

  • -draft [📌 queue requirement]
  • base=master
  • label=automerge:squash
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue squash]
      • base=master
      • any of:
        • check-pending=integration-test-result
        • check-success=integration-test-result
        • label=bypass:integration
      • check-success=breakage
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: rebase and autosquash (rebase)

  • -draft
  • base=master
  • label=automerge:rebase
  • any of:
    • -linear-history
    • check-failure=no-fixup-commits
  • any of:
    • #commits > 1 [📌 rebase requirement]
    • #commits-behind > 0 [📌 rebase requirement]
    • -linear-history [📌 rebase requirement]
  • #commits-behind=0
  • -closed [📌 rebase requirement]
  • -conflict [📌 rebase requirement]
  • queue-position = -1 [📌 rebase requirement]
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

View more details on Mergify