Skip to content
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

Migrate to Github Pages and Regenerate historical docs #1035

Closed
Eric-Arellano opened this issue Dec 1, 2023 · 4 comments
Closed

Migrate to Github Pages and Regenerate historical docs #1035

Eric-Arellano opened this issue Dec 1, 2023 · 4 comments

Comments

@Eric-Arellano
Copy link
Contributor

Per Qiskit/ecosystem#611, we accidentally deleted all ecosystem subsites when sunsetting qiskit.org.

Rustworkx is live, but the historical API docs are not yet for 0.8 - 0.13.

If any of these fail to build, we should modify this to start later and redeploy the docs for the current version, so that the bad release doesn't show up in the left sidebar:

start_version = (0, 8, 0)

@IvanIsCoding IvanIsCoding changed the title Regenerate historical docs Migrate to Github Pages and Regenerate historical docs Dec 3, 2023
@IvanIsCoding
Copy link
Collaborator

IvanIsCoding commented Dec 4, 2023

To complete this move we will need to:

@Eric-Arellano
Copy link
Contributor Author

Hey @IvanIsCoding, how did you deploy to https://qiskit.github.io/rustworkx/ with both the un-versioned docs and also 0.13 docs at https://qiskit.github.io/rustworkx/stable/0.13? I don't see the GH Pages code for it.

Specifically, I'm wondering if you had to upload the two subsites in one distinct run? Or you could do them separately, like first deploy unversioned, then later add /stable/0.13? I imagine adding /stable/0.13 on its own would overwrite the existing site.

@IvanIsCoding
Copy link
Collaborator

Hey @IvanIsCoding, how did you deploy to https://qiskit.github.io/rustworkx/ with both the un-versioned docs and also 0.13 docs at https://qiskit.github.io/rustworkx/stable/0.13? I don't see the GH Pages code for it.

Specifically, I'm wondering if you had to upload the two subsites in one distinct run? Or you could do them separately, like first deploy unversioned, then later add /stable/0.13? I imagine adding /stable/0.13 on its own would overwrite the existing site.

I manually created the folder under the gh-pages branch. Essentially, the workflow to deploy the latest version needs to always keep the stable/ folder. And the workflow to deploy a stable version shouldn't touch the latest code and should just create a new folder

@IvanIsCoding
Copy link
Collaborator

Concluded with #1037 and #1052

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants