-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
stable
to point to long-lived release branch
#4305
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
Comments
Not sure about this, maybe is part of the bug solved in #3913 (isn't deployed yet), or something else. Did you try wiping the environment before triggering a build? (Versions -> Edit -> Wipe) |
I wiped What's the time frame on deploying #3913? |
@mpharrigan hopefully in one or two weeks I think, as you can see we don't have a specific time https://docs.readthedocs.io/en/latest/changelog.html |
Thanks, I'll report back when that fix is deployed |
@mpharrigan this fix was already deployed, can you test if that really solves your problem? You may need to wipe and rebuild another version. You need to do some additional steps if that doesn't work #3913 (comment) |
No, it didn't seem to work. I tried various combinations of wiping and activate-deactivating the |
Ok, I just imported your project locally, and indeed, this is another problem. We give priority to tags, even if they are inactive. |
This was proposed in #3331 Selecting the |
Is this the intended behavior? |
Yes, this is intended. You will need to remove all tags to rtd select the branch :/ |
Ah that's a bummer. I think the docs (quoted in my original post) should be changed then |
Details
Expected Result
Under "Versions" in the RTD docs, it says
Our project (https://github.com/rigetticomputing/pyquil) has a branch called
1.9
which we update with doc fixes. There is also a tag namedv1.9.0
that is set to inactive on RTD. There are other tags which are all disabled. I would expectstable
to track the tip of branch1.9
Actual Result
RTD builds docs for the
1.9
branch just fine butstable
still points to the (inactive)v1.9.0
tagThe text was updated successfully, but these errors were encountered: