Skip to content

chore(deps): upgrade configuration

Mergify / Summary succeeded Mar 11, 2024 in 1s

2 rules match

βœ… Rule: Automatic merge on approval and successful build (delete_head_branch)

  • #approved-reviews-by>=1
  • -label~=(do-not-merge)
  • closed [πŸ“Œ delete_head_branch requirement]
  • status-success=build

βœ… Rule: Automatic merge on approval and successful build (queue)

  • #approved-reviews-by>=1
  • -draft [πŸ“Œ queue requirement]
  • -label~=(do-not-merge)
  • status-success=build
  • 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>=1 [πŸ›‘ GitHub branch protection]
      • #changes-requested-reviews-by=0 [πŸ›‘ GitHub branch protection]
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success=build
        • check-neutral=build
        • check-skipped=build
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success=DCO
        • check-neutral=DCO
        • check-skipped=DCO

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

πŸš€Β Β You can help us by becoming a sponsor!


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