Bump jinja2 from 3.1.4 to 3.1.5 in /tools/performance/engine-benchmarks/bench_tool #11941
Mergify / Summary
succeeded
Dec 25, 2024 in 1s
2 potential rules
Rule: Automatic merge on approval (merge)
-
#approved-reviews-by >= 1
[🛡 GitHub branch protection] -
branch-protection-review-decision = APPROVED
[🛡 GitHub branch protection] -
label=CI: Ready to merge
- any of: [🛡 GitHub branch protection]
-
check-neutral = Changelog
-
check-skipped = Changelog
-
check-success = Changelog
-
-
#changes-requested-reviews-by = 0
[🛡 GitHub branch protection] -
-closed
[📌 merge requirement] -
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
- any of: [🛡 GitHub branch protection]
-
check-success = license/cla
-
check-neutral = license/cla
-
check-skipped = license/cla
-
- any of: [🛡 GitHub branch protection]
-
check-success = Test Formatting
-
check-neutral = Test Formatting
-
check-skipped = Test Formatting
-
- any of: [🛡 GitHub branch protection]
-
check-success = GUI Required Checks
-
check-neutral = GUI Required Checks
-
check-skipped = GUI Required Checks
-
- any of: [🛡 GitHub branch protection]
-
check-success = Engine Required Checks
-
check-neutral = Engine Required Checks
-
check-skipped = Engine Required Checks
-
- any of: [🛡 GitHub branch protection]
-
check-success = IDE Required Checks
-
check-neutral = IDE Required Checks
-
check-skipped = IDE Required Checks
-
- any of: [🛡 GitHub branch protection]
-
check-success = WASM Required Checks
-
check-neutral = WASM Required Checks
-
check-skipped = WASM Required Checks
-
Rule: Automatic PR update (update)
-
#commits-behind > 0
[📌 update requirement] - any of:
-
label=CI: Keep up to date
-
-
-closed
[📌 update requirement] -
-conflict
[📌 update requirement] -
queue-position = -1
[📌 update requirement]
💖 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
Loading