Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Fix Select.attachedTo (backport #4458) #4461

Merged
merged 3 commits into from
Nov 25, 2024

Merge branch '6.x' into mergify/bp/6.x/pr-4458

d511fe5
Select commit
Loading
Failed to load commit list.
Merged

Fix Select.attachedTo (backport #4458) #4461

Merge branch '6.x' into mergify/bp/6.x/pr-4458
d511fe5
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 25, 2024 in 0s

1 potential rule

⚠️ The pull request has been merged by @chiselbot

‼️ Action Required ‼️

The configuration uses the deprecated update_method attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

‼️ Action Required ‼️

The configuration uses the deprecated update_bot_account attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

‼️ Action Required ‼️

The configuration uses the deprecated merge_method attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

Rule: automatic squash-and-mege of 6.x backport PRs (queue)

  • -closed [📌 queue requirement]
  • #changes-requested-reviews-by=0
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • base=6.x
  • label!="DO NOT MERGE"
  • label!="bp-conflict"
  • label="Backport"
  • status-success=all tests passed
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • any of: [🛡 GitHub branch protection]
        • check-success = all tests passed
        • check-neutral = all tests passed
        • check-skipped = all tests passed
      • any of: [🛡 GitHub branch protection]
        • check-success = EasyCLA
        • check-neutral = EasyCLA
        • check-skipped = EasyCLA
💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

9 not applicable rules

Rule: automatic squash-and-merge on CI success and review (queue)

  • #approved-reviews-by>=1
  • -closed [📌 queue requirement]
  • base=main
  • label="Please Merge"
  • #changes-requested-reviews-by=0
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • label!="DO NOT MERGE"
  • label!="bp-conflict"
  • status-success=all tests passed
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • any of: [🛡 GitHub branch protection]
        • check-success = all tests passed
        • check-neutral = all tests passed
        • check-skipped = all tests passed
      • any of: [🛡 GitHub branch protection]
        • check-success = EasyCLA
        • check-neutral = EasyCLA
        • check-skipped = EasyCLA

Rule: backport to 6.x (backport)

  • base=main
  • milestone=6.x
  • merged
  • merged [📌 backport requirement]

Rule: backport to 6.x (label)

  • base=main
  • milestone=6.x
  • merged

Rule: backport to 5.x, 6.x (backport)

  • base=main
  • milestone=5.x
  • merged
  • merged [📌 backport requirement]

Rule: backport to 5.x, 6.x (label)

  • base=main
  • milestone=5.x
  • merged

Rule: backport to 3.6.x, 5.x, 6.x (backport)

  • base=main
  • milestone=3.6.x
  • merged
  • merged [📌 backport requirement]

Rule: backport to 3.6.x, 5.x, 6.x (label)

  • base=main
  • milestone=3.6.x
  • merged

Rule: automatic squash-and-mege of 3.6.x backport PRs (queue)

  • -closed [📌 queue requirement]
  • base=3.6.x
  • #changes-requested-reviews-by=0
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • label!="DO NOT MERGE"
  • label!="bp-conflict"
  • label="Backport"
  • status-success=all tests passed
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • any of: [🛡 GitHub branch protection]
        • check-success = all tests passed
        • check-neutral = all tests passed
        • check-skipped = all tests passed
      • any of: [🛡 GitHub branch protection]
        • check-success = EasyCLA
        • check-neutral = EasyCLA
        • check-skipped = EasyCLA

Rule: automatic squash-and-mege of 5.x backport PRs (queue)

  • -closed [📌 queue requirement]
  • base=5.x
  • #changes-requested-reviews-by=0
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • label!="DO NOT MERGE"
  • label!="bp-conflict"
  • label="Backport"
  • status-success=all tests passed
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • any of: [🛡 GitHub branch protection]
        • check-success = all tests passed
        • check-neutral = all tests passed
        • check-skipped = all tests passed
      • any of: [🛡 GitHub branch protection]
        • check-success = EasyCLA
        • check-neutral = EasyCLA
        • check-skipped = EasyCLA
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