fix(stackdriver): handle null timeSeries and empty points (backport #1047) #1049
Mergify / Summary
succeeded
Aug 13, 2024 in 1s
1 rule matches and 2 potential 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: Automatically merge release branch changes on CI success and release manager review (queue)
-
label=ready to merge
-
-draft
[📌 queue requirement] -
approved-reviews-by=@release-managers
-
base~=^release-
-
status-success=build
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]- any of: [🛡 GitHub branch protection]
-
check-success=build
-
check-neutral=build
-
check-skipped=build
-
- any of: [🛡 GitHub branch protection]
-
check-success=Integration-tests (Management)
-
check-neutral=Integration-tests (Management)
-
check-skipped=Integration-tests (Management)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Integration-tests (Swagger)
-
check-neutral=Integration-tests (Swagger)
-
check-skipped=Integration-tests (Swagger)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
check-neutral=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
check-skipped=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
check-neutral=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
check-skipped=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
check-neutral=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
check-skipped=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
check-neutral=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
check-skipped=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
Rule: Automatically merge release branch changes on CI success and release manager review (label)
-
label=ready to merge
-
approved-reviews-by=@release-managers
-
base~=^release-
-
status-success=build
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
7 not applicable rules
Rule: Automatically merge PRs from maintainers on CI success and review (queue)
-
author=@oss-approvers
-
base=master
-
label=ready to merge
-
-draft
[📌 queue requirement] -
status-success=build
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]- any of: [🛡 GitHub branch protection]
-
check-success=build
-
check-neutral=build
-
check-skipped=build
-
- any of: [🛡 GitHub branch protection]
-
check-success=Integration-tests (Management)
-
check-neutral=Integration-tests (Management)
-
check-skipped=Integration-tests (Management)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Integration-tests (Swagger)
-
check-neutral=Integration-tests (Swagger)
-
check-skipped=Integration-tests (Swagger)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
check-neutral=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
check-skipped=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
check-neutral=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
check-skipped=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
check-neutral=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
check-skipped=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
check-neutral=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
check-skipped=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
Rule: Automatically merge PRs from maintainers on CI success and review (label)
-
author=@oss-approvers
-
base=master
-
label=ready to merge
-
status-success=build
Rule: Automatically merge autobump PRs on CI success (queue)
-
author:spinnakerbot
-
label~=autobump-*
-
-draft
[📌 queue requirement] -
base~=^(master|release-)
-
status-success=build
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]- any of: [🛡 GitHub branch protection]
-
check-success=build
-
check-neutral=build
-
check-skipped=build
-
- any of: [🛡 GitHub branch protection]
-
check-success=Integration-tests (Management)
-
check-neutral=Integration-tests (Management)
-
check-skipped=Integration-tests (Management)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Integration-tests (Swagger)
-
check-neutral=Integration-tests (Swagger)
-
check-skipped=Integration-tests (Swagger)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
check-neutral=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
check-skipped=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
check-neutral=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
check-skipped=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
check-neutral=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
check-skipped=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
check-neutral=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
check-skipped=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
Rule: Automatically merge autobump PRs on CI success (label)
-
author:spinnakerbot
-
label~=autobump-*
-
base~=^(master|release-)
-
status-success=build
Rule: Automatically merge on CI success and review (queue)
-
base=master
-
label=ready to merge
-
-draft
[📌 queue requirement] -
approved-reviews-by=@oss-approvers
-
status-success=build
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]- any of: [🛡 GitHub branch protection]
-
check-success=build
-
check-neutral=build
-
check-skipped=build
-
- any of: [🛡 GitHub branch protection]
-
check-success=Integration-tests (Management)
-
check-neutral=Integration-tests (Management)
-
check-skipped=Integration-tests (Management)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Integration-tests (Swagger)
-
check-neutral=Integration-tests (Swagger)
-
check-skipped=Integration-tests (Swagger)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
check-neutral=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
check-skipped=Provider-Integration-tests (Graphite, canaryAnalysisIsFailed)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
check-neutral=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
check-skipped=Provider-Integration-tests (Graphite, canaryAnalysisIsSuccessful)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
check-neutral=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
check-skipped=Provider-Integration-tests (Prometheus, canaryAnalysisIsFailed)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
check-neutral=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
check-skipped=Provider-Integration-tests (Prometheus, canaryAnalysisIsSuccessful)
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
Rule: Automatically merge on CI success and review (label)
-
base=master
-
label=ready to merge
-
approved-reviews-by=@oss-approvers
-
status-success=build
Rule: Request reviews for autobump PRs on CI failure (request_reviews)
-
base=master
-
label~=autobump-*
-
status-failure=build
-
base~=^(master|release-)
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