fix!(trace): simplify tracing and only write data in complete batches #1437
1 potential rule
The configuration uses the deprecated
commit_message_template
attribute of the queue action in one or morepull_request_rules
. It must now be used under thequeue_rules
configuration.
A brownout is planned on August 26th, 2024.
This option will be removed on September 23rd, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
The configuration uses the deprecated
merge_method
attribute of the queue action in one or morepull_request_rules
. It must now be used under thequeue_rules
configuration.
A brownout is planned on August 26th, 2024.
This option will be removed on September 23rd, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
### Rule: Automerge to v0.34.x-celestia (queue)
-
-draft
[📌 queue requirement] -
label=S:automerge
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by>=2
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success=tests (00)
-
check-neutral=tests (00)
-
check-skipped=tests (00)
-
- any of: [🛡 GitHub branch protection]
-
check-success=tests (01)
-
check-neutral=tests (01)
-
check-skipped=tests (01)
-
- any of: [🛡 GitHub branch protection]
-
check-success=tests (02)
-
check-neutral=tests (02)
-
check-skipped=tests (02)
-
- any of: [🛡 GitHub branch protection]
-
check-success=tests (03)
-
check-neutral=tests (03)
-
check-skipped=tests (03)
-
- any of: [🛡 GitHub branch protection]
-
check-success=e2e-test
-
check-neutral=e2e-test
-
check-skipped=e2e-test
-
-
- all of: [📌 queue conditions of queue
-
base=v0.34.x-celestia
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
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