Skip to content
Mergify / Summary succeeded May 3, 2024 in 0s

no rules match, no planned actions

โš ๏ธ The pull request has been merged by @tkxkd0159


๐Ÿ’–ย ย Mergify is proud to provide this service for free to open source projects.

๐Ÿš€ย ย You can help us by becoming a sponsor!


3 not applicable rules

Rule: automerge to main with label automerge and branch protection passing (queue)

  • base=main
  • label=automerge
  • #approved-reviews-by>1
  • -draft [๐Ÿ“Œ queue requirement]
  • any of: [๐Ÿ“Œ queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [๐Ÿ”€ queue conditions]
    • all of: [๐Ÿ“Œ queue conditions of queue default]
      • #approved-reviews-by>=2 [๐Ÿ›ก GitHub branch protection]
      • #changes-requested-reviews-by=0 [๐Ÿ›ก GitHub branch protection]
      • #review-threads-unresolved=0 [๐Ÿ›ก GitHub branch protection]

Rule: backport patches to v0.48.x branch (backport)

  • base=main
  • label=backport/v0.48.x
  • merged [๐Ÿ“Œ backport requirement]

Rule: backport patches to v0.47.x branch (backport)

  • base=main
  • label=backport/v0.47.x
  • merged [๐Ÿ“Œ backport 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