[v23.3.x] archival: Delete replaced segments during spillover GC #16167
Mergify / Summary
succeeded
Jan 19, 2024 in 1s
no rules match, no planned actions
1 not applicable rule
Rule: enqueue on label (queue)
-
base=dev
-
label=merge-queue
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
dev
]- any of: [🛡 GitHub branch protection]
-
check-neutral=ducktape-build-release-clang-amd64
-
check-skipped=ducktape-build-release-clang-amd64
-
check-success=ducktape-build-release-clang-amd64
-
-
#approved-reviews-by>=1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success=build-debug-clang-amd64
-
check-neutral=build-debug-clang-amd64
-
check-skipped=build-debug-clang-amd64
-
- any of: [🛡 GitHub branch protection]
-
check-success=build-release-clang-amd64
-
check-neutral=build-release-clang-amd64
-
check-skipped=build-release-clang-amd64
-
- any of: [🛡 GitHub branch protection]
-
check-success=ducktape-build-debug-clang-amd64
-
check-neutral=ducktape-build-debug-clang-amd64
-
check-skipped=ducktape-build-debug-clang-amd64
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
-
-draft
[📌 queue requirement] -
-mergify-configuration-changed
[📌 queue -> allow_merging_configuration_change setting 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