Thanks to visit codestin.com
Credit goes to github.com

Skip to content

DOC: Update meson-python intersphinx link #29005

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

Merged
merged 1 commit into from
Oct 22, 2024

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Oct 22, 2024

PR summary

The old one is getting readthedocs' pseudo-redirect with an HTML page.

PR checklist

The old one is getting readthedocs' pseudo-redirect with an HTML page.
@QuLogic QuLogic added this to the v3.9.3 milestone Oct 22, 2024
@github-actions github-actions bot added the Documentation: build building the docs label Oct 22, 2024
@timhoffm timhoffm modified the milestones: v3.9.3, v3.9-doc Oct 22, 2024
@timhoffm timhoffm merged commit ac1d009 into matplotlib:main Oct 22, 2024
25 of 27 checks passed
Copy link

lumberbot-app bot commented Oct 22, 2024

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
git checkout v3.9.x
git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 ac1d0096c1eb27aba1a79b7d5e0f3f8c44ee7119
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #29005: DOC: Update meson-python intersphinx link'
  1. Push to a named branch:
git push YOURFORK v3.9.x:auto-backport-of-pr-29005-on-v3.9.x
  1. Create a PR against branch v3.9.x, I would have named this PR:

"Backport PR #29005 on branch v3.9.x (DOC: Update meson-python intersphinx link)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

Copy link

lumberbot-app bot commented Oct 22, 2024

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
git checkout v3.9.2-doc
git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 ac1d0096c1eb27aba1a79b7d5e0f3f8c44ee7119
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #29005: DOC: Update meson-python intersphinx link'
  1. Push to a named branch:
git push YOURFORK v3.9.2-doc:auto-backport-of-pr-29005-on-v3.9.2-doc
  1. Create a PR against branch v3.9.2-doc, I would have named this PR:

"Backport PR #29005 on branch v3.9.2-doc (DOC: Update meson-python intersphinx link)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

@QuLogic QuLogic deleted the doc-meson-intersphinx branch October 22, 2024 09:38
QuLogic pushed a commit to QuLogic/matplotlib that referenced this pull request Oct 22, 2024
tacaswell added a commit that referenced this pull request Oct 22, 2024
…3.9.x

Backport PR #29005 on branch v3.9.x (DOC: Update meson-python intersphinx link)
@QuLogic QuLogic modified the milestones: v3.9-doc, v3.9.3 Jul 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation: build building the docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants