-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Various documentation updates #8955
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
Conversation
@@ -6,11 +6,9 @@ A legend entry can now contain more than one legend key. The extended | |||
legend area in the specified number of sections; ``pad`` changes the padding | |||
between the legend keys. | |||
|
|||
.. figure:: ../../gallery/pylab_examples/images/sphx_glr_legend_demo6_001.png | |||
:target: ../../gallery/pylab_examples/legend_demo6.html | |||
.. figure:: /gallery/text_labels_and_annotations/images/sphx_glr_legend_demo_004.png |
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.
PS, @choldgraf for these, we don't need the ../..
because Sphinx accepts an absolute path. Unfortunately, it doesn't work on the target below though.
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.
that's good to know! thanks
Oops, I forgot the currently released version of sphinx-gallery doesn't support http:// links properly, so I reverted that bit. Hopefully should build now. |
@@ -48,7 +48,10 @@ Review and commit changes. Some issue/PR titles may not be valid rst (the most | |||
Check Docs | |||
---------- | |||
|
|||
Before tagging, make sure that the docs build cleanly :: | |||
Before tagging, update the what's new listing in :file:`doc/users/whats_new.rst` |
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 think it should be done in this PR, but I still think it'd be good to have some kind of "credit" system for various features. E.g. just making sure that every new feature or bugfix has a by XXX
at the end, optionally with a link to a user webpage or something.
Almost all of this LGTM. The one thing I'm a little concerned about is having a |
This removes a conflict in Sphinx which can't see both the file and the directory with the same name.
This allows us to check that they're written correctly before getting around to a release.
I renamed it to |
👍 doing that with the whats_new folder has been on my list of things to get to for a while! |
Then I say let's do it...tests are passing and I think the new folder naming works great |
Thanks @QuLogic !!! 🎉 |
Fingers crossed on the deploy this time... |
PR Summary
These are some minor preemptive corrections to the docs.
Firstly, import the unreleased What's New? entries into the docs so we can see what the output is like. There was one bug in there that I fixed. Unfortunately, Sphinx cannot see both a
whats_new.rst
file and awhats_new/
directory, so I had to rename one. I hope the instructions are reasonable for a release step @tacaswell.Secondly, due to sphinx-gallery/sphinx-gallery#250, several things that were just printed out are now real Sphinx warnings, which will fail with our default build setup. I corrected the back-reference URLs so that sphinx-gallery stops warning and creates them now. Unfortunately, this does slow the build a bit, but I'm hoping sphinx-gallery/sphinx-gallery#272 can be merged as well to help with that.
Finally, with the deploy key added on CircleCI and devdocs, enable the new key so we can push the build docs on
master
. This should fix #8875. I have tested this on my fork and CircleCI correctly uploads docs once this change is made.PR Checklist