Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Publish optimal trajectory as a Path message #4640

move path population in add_marker

676a083
Select commit
Loading
Failed to load commit list.
Merged

Publish optimal trajectory as a Path message #4640

move path population in add_marker
676a083
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Aug 27, 2024 in 0s

1 rule matches and 6 potential rules

⚠️ The pull request has been merged by @SteveMacenski

Rule: backport to jazzy at reviewers discretion (backport)

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

Rule: backport to iron at reviewers discretion (backport)

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

Rule: backport to humble at reviewers discretion (backport)

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

✅ 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