ComputeUncompute circuit transpilation option. #195
Mergify / Summary
succeeded
Aug 1, 2024 in 1s
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: automatic merge on CI success and review (queue)
-
#approved-reviews-by>=1
-
label=automerge
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
automerge
]-
#approved-reviews-by>=1
[🛡 GitHub branch protection] -
branch-protection-review-decision=APPROVED
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success=license/cla
-
check-neutral=license/cla
-
check-skipped=license/cla
-
- any of: [🛡 GitHub branch protection]
-
check-success=Checks (ubuntu-latest, 3.8)
-
check-neutral=Checks (ubuntu-latest, 3.8)
-
check-skipped=Checks (ubuntu-latest, 3.8)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Algorithms (macos-latest, 3.8)
-
check-neutral=Algorithms (macos-latest, 3.8)
-
check-skipped=Algorithms (macos-latest, 3.8)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Algorithms (ubuntu-latest, 3.9)
-
check-neutral=Algorithms (ubuntu-latest, 3.9)
-
check-skipped=Algorithms (ubuntu-latest, 3.9)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Algorithms (ubuntu-latest, 3.10)
-
check-neutral=Algorithms (ubuntu-latest, 3.10)
-
check-skipped=Algorithms (ubuntu-latest, 3.10)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Algorithms (ubuntu-latest, 3.11)
-
check-neutral=Algorithms (ubuntu-latest, 3.11)
-
check-skipped=Algorithms (ubuntu-latest, 3.11)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Algorithms (ubuntu-latest, 3.8)
-
check-neutral=Algorithms (ubuntu-latest, 3.8)
-
check-skipped=Algorithms (ubuntu-latest, 3.8)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Tutorials (ubuntu-latest, 3.8)
-
check-neutral=Tutorials (ubuntu-latest, 3.8)
-
check-skipped=Tutorials (ubuntu-latest, 3.8)
-
- any of: [🛡 GitHub branch protection]
-
check-success=coverage/coveralls
-
check-neutral=coverage/coveralls
-
check-skipped=coverage/coveralls
-
- any of: [🛡 GitHub branch protection]
-
check-success=Deprecation_Messages_and_Coverage (3.8)
-
check-neutral=Deprecation_Messages_and_Coverage (3.8)
-
check-skipped=Deprecation_Messages_and_Coverage (3.8)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Algorithms (windows-latest, 3.8)
-
check-neutral=Algorithms (windows-latest, 3.8)
-
check-skipped=Algorithms (windows-latest, 3.8)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Tutorials (ubuntu-latest, 3.12)
-
check-neutral=Tutorials (ubuntu-latest, 3.12)
-
check-skipped=Tutorials (ubuntu-latest, 3.12)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Algorithms (macos-latest, 3.12)
-
check-neutral=Algorithms (macos-latest, 3.12)
-
check-skipped=Algorithms (macos-latest, 3.12)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Algorithms (windows-latest, 3.12)
-
check-neutral=Algorithms (windows-latest, 3.12)
-
check-skipped=Algorithms (windows-latest, 3.12)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Algorithms (ubuntu-latest, 3.12)
-
check-neutral=Algorithms (ubuntu-latest, 3.12)
-
check-skipped=Algorithms (ubuntu-latest, 3.12)
-
-
- all of: [📌 queue conditions of queue
-
-draft
[📌 queue requirement] -
check-success=Deprecation_Messages_and_Coverage (3.8)
-
label!=on hold
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
Rule: backport (backport)
-
label=stable backport potential
-
merged
[📌 backport requirement]
💖 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
Loading