Fix making the build directory kept by keep-failed
readable (backport #11473)
#11480
Mergify / Summary
succeeded
Sep 16, 2024 in 1s
1 rule matches and 7 potential rules
Rule: backport patches to 2.18 (backport)
-
label=backport 2.18-maintenance
-
merged
[📌 backport requirement]
Rule: backport patches to 2.19 (backport)
-
label=backport 2.19-maintenance
-
merged
[📌 backport requirement]
Rule: backport patches to 2.20 (backport)
-
label=backport 2.20-maintenance
-
merged
[📌 backport requirement]
Rule: backport patches to 2.21 (backport)
-
label=backport 2.21-maintenance
-
merged
[📌 backport requirement]
Rule: backport patches to 2.22 (backport)
-
label=backport 2.22-maintenance
-
merged
[📌 backport requirement]
Rule: backport patches to 2.23 (backport)
-
label=backport 2.23-maintenance
-
merged
[📌 backport requirement]
Rule: backport patches to 2.24 (backport)
-
label=backport 2.24-maintenance
-
merged
[📌 backport requirement]
💖 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: merge using the merge queue (queue)
-
-closed
[📌 queue requirement] -
base=master
-
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] -
label~=merge-queue|dependencies
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]- any of: [🛡 GitHub branch protection]
-
check-skipped = installer_test
-
check-neutral = installer_test
-
check-success = installer_test
-
- any of: [🛡 GitHub branch protection]
-
check-success = tests (macos-latest)
-
check-neutral = tests (macos-latest)
-
check-skipped = tests (macos-latest)
-
- any of: [🛡 GitHub branch protection]
-
check-success = tests (ubuntu-latest)
-
check-neutral = tests (ubuntu-latest)
-
check-skipped = tests (ubuntu-latest)
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
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