DOC: Fix toc structure in explain/interactive #24187
Merged
+1
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tacaswell
approved these changes
Oct 16, 2022
|
It is failing in the docs build, but it looks like we merged some bad markup someplace else? |
|
The doc failure was introduced in #24157 due to incorrect ReST formatting. For simplicity, I've added a second commit with the fix here. |
|
I'll self-merge based on @tacaswell's positive review. |
meeseeksmachine
pushed a commit
to meeseeksmachine/matplotlib
that referenced
this pull request
Oct 16, 2022
|
Something went wrong ... Please have a look at my logs. It seems that the branch you are trying to backport to does not exist. |
oscargus
added a commit
that referenced
this pull request
Oct 16, 2022
…187-on-v3.6.x Backport PR #24187 on branch v3.6.x (DOC: Fix toc structure in explain/interactive)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Closes #22905. Not sure why we had the
.. toctree::entry there or what sphinx is doing with it. But it's not needed and without it the page becomes a structure leaf like it's sibling pages.