-
Notifications
You must be signed in to change notification settings - Fork 65
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
Docs fix #1081
Docs fix #1081
Conversation
Pull Request Test Coverage Report for Build 4895928411
💛 - Coveralls |
Note that we also want to have docs for |
Also, help me understand your Slack announcement, what is the difference between the docs here and the docs on v2.7.1? |
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.
.
I don't know what you mean by Replace this command
with |
The docs on master show the new API. The docs on v2.7.1 show the docs of the currently released v2.7, which uses the v2 API. The docs from master are not useful, as most people install the latest release from pip/conda-forge. |
OK, but shouldn't there be a separate PR for those? Am I missing something? |
There is a makefile in This allows us to remove the Until now, we had to create these files locally, then push them to |
I know all that, but I cannot touch the build commands on rtd. And as I said at the beginning, we don't need this. Repos store rst files routinely. |
2.7.1: i can't make a PR to rewrite the commit history. This is just there for now so we have useful docs until we make the next release |
Right, I checked and we can in fact customize the commands, but I agree - let's not go this far.
I see! That's fine. |
I'm merging it and I'll check if it pulls the ones from |
yes! finally they're back. Now we can point |
Ok, great. But no, I'll do that when we've released the last v2 version. |
Fixes the current docs on rtd (you can check that it is actually working here).
@nikfilippas please review, but remember we want to keep any changes here as minimal as possible. Polishing the docs or including any API improvements is for later.