Open
Conversation
Contributor
|
Thanks for contributing to Qiskit documentation! 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. Thanks! 🙌 |
abbycross
approved these changes
Mar 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates all dev APIs that changed since the last sync.
Note
This pull request was created by a GitHub action.
What is this PR?
We host "dev" API docs (e.g. https://quantum.cloud.ibm.com/docs/en/api/qiskit-ibm-runtime/dev), which are generated from the branch of the project's repo. This helps us preview upcoming changes and helps any users that are using the branch rather than a specific release.
This PR updates the dev API docs
How to deal with this PR
Glance through the diff and check things look reasonable. Only the dev docs and supporting images should be changed. It's common for there to be new pages. While sometimes a page or API will be removed, we should not be deleting a substantial portion of the docs.
If it looks good, approve the PR.
Close and re-open this PR to trigger CI; the action is not allowed to trigger CI properly so we need a human with write access to trigger it.
Once CI has passed, you can merge this PR. If something goes wrong, consider asking an engineer for help. With broken links, we sometimes need to update the original API docs to fix the bad link, such as updating the Qiskit SDK in Qiskit/qiskit.