Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix explicitly calibrated gates in GateDirection (backport #9786) #9788

Merged
merged 1 commit into from
Mar 13, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 13, 2023

This is an automatic backport of pull request #9786 done by Mergify.
Cherry-pick of c2affb1 has failed:

On branch mergify/bp/stable/0.23/pr-9786
Your branch is up to date with 'origin/stable/0.23'.

You are currently cherry-picking commit c2affb145.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   qiskit/transpiler/passes/utils/gate_direction.py
	new file:   releasenotes/notes/fix-gate-direction-calibration-c51202358d86e18f.yaml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   test/python/transpiler/test_gate_direction.py

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally


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

@mergify mergify bot requested a review from a team as a code owner March 13, 2023 16:38
@mergify mergify bot added the conflicts used by mergify when there are conflicts in a port label Mar 13, 2023
@qiskit-bot
Copy link
Collaborator

Thank you for opening a new pull request.

Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient.

While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone.

One or more of the the following people are requested to review this:

  • @Qiskit/terra-core

If there is an explicit calibration given, this overrides the generic
information from the `CouplingMap` or the `Target` for that particular
instance, since one can use pulse-level control to define gates on a
circuit-by-circuit basis that are not generically available in a way
that can be specified in the coupling or target.
@jakelishman jakelishman force-pushed the mergify/bp/stable/0.23/pr-9786 branch from bef3a13 to 549e4c6 Compare March 13, 2023 16:42
@jakelishman jakelishman added Changelog: Bugfix Include in the "Fixed" section of the changelog automerge and removed conflicts used by mergify when there are conflicts in a port labels Mar 13, 2023
@jakelishman jakelishman added this to the 0.23.3 milestone Mar 13, 2023
@mergify mergify bot merged commit 44cda51 into stable/0.23 Mar 13, 2023
@mergify mergify bot deleted the mergify/bp/stable/0.23/pr-9786 branch March 13, 2023 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changelog: Bugfix Include in the "Fixed" section of the changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants