Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Move release related docs to new sub-folder#30304

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
dstansby wants to merge3 commits intomatplotlib:main
base:main
Choose a base branch
Loading
fromdstansby:move-rel-docs

Conversation

dstansby
Copy link
Member

PR summary

See#27396.

This moves release-related docs to their own folder within the docs (/release).

PR checklist

story645 reacted with heart emoji
@jklymak
Copy link
Member

Probably this will need a 501 redirect on the server?

@dstansby
Copy link
MemberAuthor

Probably this will need a 501 redirect on the server?

Does the spinx redirect directive not handle the redirects by itself?

I can't work out why the doc build is failing. It says

    ValueError: users/release_notes_next is already noted as redirecting to release/release_notes_next

but, as far as I can see there's only one redirect from users/release_notes_next 🤔

@story645
Copy link
Member

Does the spinx redirect directive not handle the redirects by itself?

I think there's one more level handled inhttps://github.com/matplotlib/matplotlib.org

@dstansby
Copy link
MemberAuthor

Sorry, I'm not following - what does "one more level handled" mean?

@dstansby
Copy link
MemberAuthor

Since the improvements/fixes to the redirection code are orthogonal to moving these docs around, I put them in#30309

@jklymak
Copy link
Member

Ok i had not noticed that you'd put a redirect-from in each file. Seems fine if it works! I was suggesting just redirecting the subdirectory at the server config, but if this caught everything it should be ok

@story645
Copy link
Member

Sorry, I'm not following - what does "one more level handled" mean?

Just that I remember having to ask@QuLogic to do some redirects on the matplotlib.org repo for the other PRs on that issue.

dstansby reacted with thumbs up emoji

Copy link
Member

@QuLogicQuLogic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

We probably should update mpl-sphinx-theme to point to the new URLs before the next release, to avoid extra redirects.

story645 reacted with thumbs up emoji
@QuLogic
Copy link
Member

Sorry, I'm not following - what does "one more level handled" mean?

Just that I remember having to ask@QuLogic to do some redirects on the matplotlib.org repo for the other PRs on that issue.

That was stable -> devel (which means independent build directories); this is all internal to the a single build, so shouldn't need anything server side.

story645 reacted with thumbs up emoji

@dstansbydstansby marked this pull request as ready for reviewJuly 16, 2025 08:07
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@QuLogicQuLogicQuLogic approved these changes

Assignees
No one assigned
Labels
Documentation: buildbuilding the docsDocumentation: devdocsfiles in doc/devel
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@dstansby@jklymak@story645@QuLogic

[8]ページ先頭

©2009-2025 Movatter.jp