-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
added a reversing section to colormap reference #23904
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
it's very possibly on the verbose side now, but changed the reversed section in the reference to show viridis, cleaned up language, and linked out to a new reversing section in the colormap tutorial that has a |
e6b44f6
to
46af8cb
Compare
0d7e51e
to
284d9e2
Compare
b238db5
to
ce3e284
Compare
reversing + registering section to colormap tutorial removed parent notation from `reversed` methods b/c no heirarchy Co-authored-by: RutgerK <[email protected]> Co-authored-by: Tim Hoffmann <[email protected]> Co-authored-by: Jody Klymak <[email protected]> Co-authored-by: Thomas A Caswell <[email protected]>
@QuLogic these are all doc changes so shouldn't the milestone be v3.6.1/why is it 3.7.0? |
@meeseeksdev backport to v3.6.x This is not v3.6-doc because it contains changes to files in |
I only document what has occurred in merged PRs. |
So you set the milestone as 3.7.0 b/c it was merged into main?, and this would have to be backported and then changed to 3.6.1? |
@meeseeksdev backport to v3.6.1 |
Something went wrong ... Please have a look at my logs. It seems that the branch you are trying to backport to does not exist. |
oops, 3.6.1 doesn't exist yet 🤦♀️ |
@meeseeksdev backport to v3.6.x |
…904-on-v3.6.x Backport PR #23904 on branch v3.6.x (added a reversing section to colormap reference)
PR Summary
changed the note about reversing a colormap into a section of the colormap reference 'cause it was kind of buried in the preamble
PR Checklist
Tests and Styling
pytest
passes).flake8-docstrings
and runflake8 --docstring-convention=all
).Documentation
doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).