Backport PR #17141 to 8.16: Update Dockerfile.erb to set eux on RUN command with semicolons #17201
Mergify / Summary
succeeded
Feb 28, 2025 in 0s
3 potential rules
Rule: ask to resolve conflict (comment)
-
conflict
Rule: remove backport-skip label (label)
-
label~=^backport-\d
Rule: remove backport-8.x label if backport-skip is present (label)
-
label~=^backport-skip
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
6 not applicable rules
Rule: notify the backport has not been merged yet (comment)
-
-closed
-
-merged
-
author=mergify[bot]
-
schedule=Mon-Mon 06:00-10:00[Europe/Paris]
-
#check-success>0
Rule: notify the backport policy (comment)
-
-label~=^backport
-
base=main
Rule: add backport-8.x for the all the PRs targeting main if no skipped or assigned already (comment, label)
-
base=main
-
-label~=^(backport-skip|backport-8.x)$
Rule: backport patches to 8.x branch (backport)
-
base=main
-
label=backport-8.x
-
merged
-
merged
[📌 backport requirement]
Rule: backport patches to 8.16 branch (backport)
-
base=main
-
label=backport-8.16
-
merged
-
merged
[📌 backport requirement]
Rule: backport patches to 8.17 branch (backport)
-
base=main
-
label=backport-8.17
-
merged
-
merged
[📌 backport requirement]
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