Skip to content

merge queue: embarking main (5af0733) and #820 together #832

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jul 14, 2025

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (5af0733) and #820 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #820.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

Required conditions to stay in the queue:

---
previous_failed_batches: []
pull_requests:
  - number: 820
...

black-dragon74 and others added 4 commits June 24, 2025 19:44
Signed-off-by: Niraj Yadav <niryadav@redhat.com>
This patch refactors the schedule-precedence logic
to allow the value to be overridden by a ConfigMap.

The default mode of operation still prefers PVCs first
as source of key rotation and reclaimspace annotations.

The values for `schedule-precedence` keys are now concretely
defined as either `pvc` or `storageclass`.

Signed-off-by: Niraj Yadav <niryadav@redhat.com>
This patch adds PendingReleaseNotes to track upcoming changes in
release notes.

Signed-off-by: Niraj Yadav <niryadav@redhat.com>
@mergify mergify bot closed this Jul 14, 2025
@mergify mergify bot deleted the mergify/merge-queue/bb90e52ea6 branch July 14, 2025 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant