Skip to content

Apply errchkjson, tenv

Mergify / Summary succeeded Jun 12, 2024 in 0s

4 potential rules

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

  • #approved-reviews-by>1
  • -draft [πŸ“Œ queue requirement]
  • label=automerge
  • 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]
  • base=main
  • any of: [πŸ“Œ queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed

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

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

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

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

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

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

πŸ’–Β Β 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