✨Add continuous testing workflow for Qiskit main branch #860
Conversation
This file contains 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
burgholzer
added
continuous integration
burgholzer
force-pushed
the
upstream-qiskit-workflow
branch
2 times, most recently
from
52ada37 to
6db7726
Compare
…it main branch Signed-off-by: burgholzer <burgholzer@me.com>
burgholzer
force-pushed
the
upstream-qiskit-workflow
branch
from
6db7726 to
a118f91
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This pull request introduces a continuous testing workflow to ensure compatibility with the latest changes in the Qiskit main branch. This addition aims to maintain project stability and address potential integration issues promptly.
This is especially critical in light of the upcoming Qiskit 2.0 release.
The respective workflow will run once a week, on pull requests that change the respective file, as well as on manual workflow triggers.
Checklist: