-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Remove unneeded Sphinx templates and static files #9712
Conversation
These files are several files left over from old versions of the documentation, and several from before `qiskit-sphinx-theme` was entirely separate from the Terra docs-build process. Having them remain in the repository causes local (or CI) builds of the documentation to pull from these templates instead of those provided by the theme package, which causes us to get different behaviour to what will actually be deployed during the metapackage docs build.
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:
|
Pull Request Test Coverage Report for Build 4323873994
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense to me these templates are locally overriding things for no reason, we should keep in sync with the theme layout for these builds. At some point this will get more important when there is a unified docs build here without a metapackage and the terra docs builds are what get published.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent, thank you! cc @javabster - perhaps this explains some docs behavior?
These files are several files left over from old versions of the documentation, and several from before `qiskit-sphinx-theme` was entirely separate from the Terra docs-build process. Having them remain in the repository causes local (or CI) builds of the documentation to pull from these templates instead of those provided by the theme package, which causes us to get different behaviour to what will actually be deployed during the metapackage docs build. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 40f73a3)
These files are several files left over from old versions of the documentation, and several from before `qiskit-sphinx-theme` was entirely separate from the Terra docs-build process. Having them remain in the repository causes local (or CI) builds of the documentation to pull from these templates instead of those provided by the theme package, which causes us to get different behaviour to what will actually be deployed during the metapackage docs build. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 40f73a3) Co-authored-by: Jake Lishman <jake.lishman@ibm.com>
These files are several files left over from old versions of the documentation, and several from before `qiskit-sphinx-theme` was entirely separate from the Terra docs-build process. Having them remain in the repository causes local (or CI) builds of the documentation to pull from these templates instead of those provided by the theme package, which causes us to get different behaviour to what will actually be deployed during the metapackage docs build. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Summary
These files are several files left over from old versions of the documentation, and several from before
qiskit-sphinx-theme
was entirely separate from the Terra docs-build process. Having them remain in the repository causes local (or CI) builds of the documentation to pull from these templates instead of those provided by the theme package, which causes us to get different behaviour to what will actually be deployed during the metapackage docs build.Details and comments
Found during the process of writing the bugfix Qiskit/qiskit_sphinx_theme#197. Other Qiskit projects may well want to copy the spirit of this PR if they haven't already, in particular ensuring that they're not providing a
layout.html
template that overrides the up-to-date, unified one provided byqiskit_sphinx_theme
(though likely everyone will want to get rid of everything intemplates
except for theirautosummary
settings).