Skip to content

Prevent a possible segmentation fault

Mergify / Summary succeeded Feb 26, 2024 in 0s

8 potential rules

Rule: backport to iron at reviewers discretion (backport)

  • label=backport-iron
  • merged [📌 backport requirement]
  • base=main

Rule: backport to humble at reviewers discretion (backport)

  • label=backport-humble
  • merged [📌 backport requirement]
  • base=main

Rule: backport to galactic at reviewers discretion (backport)

  • label=backport-galactic
  • merged [📌 backport requirement]
  • base=main

Rule: backport to foxy at reviewers discretion (backport)

  • label=backport-foxy
  • merged [📌 backport requirement]
  • base=main

Rule: delete head branch after merge (delete_head_branch)

  • closed [📌 delete_head_branch requirement]
  • merged

Rule: ask to resolve conflict (comment)

  • conflict
  • author!=mergify

Rule: Main build failures (comment)

  • any of:
    • check-failure=ci/circleci: debug_build
    • check-failure=ci/circleci: release_build
  • base=main

Rule: Removed maintainer checklist (comment)

  • all of:
    • body-raw~=^#### For Maintainers
    • author!=SteveMacenski
    • author!=mergify

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


1 not applicable rule

Rule: development targets main branch (comment)

  • base!=main
  • author!=SteveMacenski
  • author!=mergify
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