chore: Update test-examples workflow#953
Merged
Merged
Mergify / Summary
succeeded
Jul 4, 2026 in 0s
1 potential rule
commit_message_template is deprecated and will be removed on 2026-09-30. Use the declarative commit_message_format instead: https://docs.mergify.com/workflow/actions/merge#migrating-from-commit_message_template
Rule: Automatic merge on approval and successful build (queue)
-
-closed[📌 queue requirement] -
#approved-reviews-by>=1 -
-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 -
status-success=test-examples - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue rule
default]-
#approved-reviews-by>=1 -
-label~=(do-not-merge) -
github-review-approved[🛡 GitHub branch protection] -
status-success=build -
status-success=package-dotnet -
status-success=package-go -
status-success=package-java -
status-success=package-js -
status-success=package-python -
status-success=test-examples
-
- all of: [📌 queue conditions of queue rule
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