-
Notifications
You must be signed in to change notification settings - Fork 58
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
Deploy docs to GitHub Pages #115
Conversation
FYI for CI failure see issue |
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.
Thanks Arnau for the PR, let's wait for testing-cabal/testtools#371 and see if the CI gets fixed once it's merged.
Once this is done the first section in the README, about installation, will need its link updating. |
Pull Request Test Coverage Report for Build 7492816091
💛 - 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.
@arnaucasau I have done a couple of workarounds to avoid the CI failures and as a result this can be moved forwards now. I think it's ready right.
Just as clarification, as I understand it, publishing is a 2 step process now, not just running this workflow. But now once its run the pages deployed to gh-pages need a second manual step to be published?
Great, thank you @woodsp-ibm! Regarding your question, I guess when you say publish it, you mean to We only need the first of the two steps you mentioned. With this workflow, the docs will be deployed to GitHub Pages where the documentation will live, and once this change is done, I will set up the redirects from |
@arnaucasau I was reading it was "deployed" to a |
Co-authored-by: Steve Wood <[email protected]> (cherry picked from commit 402e470)
Oh, I see what you meant now. Exactly, we only need to deploy to the |
Co-authored-by: Arnau Casau <[email protected]>
@arnaucasau Ok, I ran the workflow, updated the Settings and the docs are now live https://qiskit-community.github.io/qiskit-algorithms/ I guess a redirect for former ecosystem url can be done now. |
Summary
This PR changes the
deploy-docs.yml
workflow to deploy the documentation to GitHub Pages to migrate the project away from the qiskit.org domain.More information about the change and a quick guide to set up GitHub pages can be found at: Qiskit/ecosystem#578
Reminder task for maintainers here to update the doc link in the About text for the repo on the main page once this change happens and the docs are re-deployed . This will need backporting to stable to have it apply to present docs version before it can be re-run.