feat: allow use of alternate KMS keys#731
Open
MorganPattersonSignet wants to merge 1 commit into
Open
This check has been archived and is scheduled for deletion.
Learn more about checks retention
Mergify / Summary
succeeded
Aug 4, 2025 in 0s
2 potential rules
Rule: Automatic merge on approval and successful build (delete_head_branch)
-
#approved-reviews-by>=1 -
closed[📌 delete_head_branch requirement] -
-label~=(do-not-merge) -
status-success=build -
status-success=package-dotnet -
status-success=package-go -
status-success=package-java -
status-success=package-js -
status-success=package-python
Rule: Automatic merge on approval and successful build (queue)
-
#approved-reviews-by>=1 - any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default]-
#approved-reviews-by>=1 -
-label~=(do-not-merge) -
status-success=build -
status-success=package-dotnet -
status-success=package-go -
status-success=package-java -
status-success=package-js -
status-success=package-python
-
- all of: [📌 queue conditions of queue
-
-closed[📌 queue requirement] -
-conflict[📌 queue requirement] -
-draft[📌 queue requirement] -
-label~=(do-not-merge) -
status-success=build -
status-success=package-dotnet -
status-success=package-go -
status-success=package-java -
status-success=package-js -
status-success=package-python - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill 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