Fix isCurrent in obstacle layer and assure CostmapTopicCollisionChecker only uses current costmaps #4800
+7
−6
Mergify / Summary
succeeded
Jul 31, 2025 in 2s
8 potential rules
Rule: backport to jazzy at reviewers discretion (backport)
-
label=backport-jazzy
-
merged
[📌 backport requirement] -
base=main
Rule: backport to humble-main at reviewers discretion (backport)
-
label=backport-humble-main
-
merged
[📌 backport requirement] -
base=main
Rule: backport to humble at reviewers discretion (backport)
-
label=backport-humble
-
merged
[📌 backport requirement] -
base=main
Rule: backport to kilted at reviewers discretion (backport)
-
label=backport-kilted
-
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
-
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
Loading