-
Notifications
You must be signed in to change notification settings - Fork 86
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
After Qiskit 1.1 release, run TocGrouping.test.ts on stable docs #1341
Labels
Comments
github-merge-queue bot
pushed a commit
that referenced
this issue
May 12, 2024
The Qiskit devs were worried about the index page from Qiskit/qiskit#12333 falling out of sync with our custom grouping for `_toc.json`. This PR adds a test to ensure that the two files are in sync. In particular, it checks that the grouping and sequence of modules is identical. It does not check that the label for the groups are the same, though. For now, we only check the dev docs because the latest docs (1.0) fail. #1341 will also start checking the latest docs once 1.1 is released.
frankharkins
pushed a commit
to frankharkins/documentation
that referenced
this issue
Jul 22, 2024
The Qiskit devs were worried about the index page from Qiskit/qiskit#12333 falling out of sync with our custom grouping for `_toc.json`. This PR adds a test to ensure that the two files are in sync. In particular, it checks that the grouping and sequence of modules is identical. It does not check that the label for the groups are the same, though. For now, we only check the dev docs because the latest docs (1.0) fail. Qiskit#1341 will also start checking the latest docs once 1.1 is released.
frankharkins
pushed a commit
to frankharkins/documentation
that referenced
this issue
Jul 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a follow up to #1300. Once we switch Qiskit 1.1 to be the stable release, we should run that test on
latest
,dev
, and generic code for the historical APIs starting with 1.1 and newer.The text was updated successfully, but these errors were encountered: