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

DOC: update switcher for 3.10#29360

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

Merged
greglucas merged 1 commit intomatplotlib:mainfromtacaswell:doc/fix_switcher
Dec 20, 2024

Conversation

tacaswell
Copy link
Member

closes#29359

@tacaswelltacaswell added this to thev3.10.0-doc milestoneDec 20, 2024
@greglucasgreglucas merged commit06add21 intomatplotlib:mainDec 20, 2024
19 of 21 checks passed
@lumberbot-appLumberbot (App)
Copy link

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.10.xgit pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 06add21e34dd25a19528aa84c82e72b8af5bb541
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #29360: DOC: update switcher for 3.10'
  1. Push to a named branch:
git push YOURFORK v3.10.x:auto-backport-of-pr-29360-on-v3.10.x
  1. Create a PR against branch v3.10.x, I would have named this PR:

"Backport PR#29360 on branch v3.10.x (DOC: update switcher for 3.10)"

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 theStill Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free tosuggest an improvement.

@tacaswell
Copy link
MemberAuthor

the mypy failures should be fixed by#29362

@tacaswelltacaswell deleted the doc/fix_switcher branchDecember 20, 2024 20:56
@lumberbot-appLumberbot (App)
Copy link

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.10.0-docgit pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 06add21e34dd25a19528aa84c82e72b8af5bb541
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #29360: DOC: update switcher for 3.10'
  1. Push to a named branch:
git push YOURFORK v3.10.0-doc:auto-backport-of-pr-29360-on-v3.10.0-doc
  1. Create a PR against branch v3.10.0-doc, I would have named this PR:

"Backport PR#29360 on branch v3.10.0-doc (DOC: update switcher for 3.10)"

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 theStill Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free tosuggest an improvement.

@QuLogic
Copy link
Member

There is no need to backport this; the version frommain is used.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@jklymakjklymakjklymak approved these changes

@greglucasgreglucasgreglucas approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v3.11.0
Development

Successfully merging this pull request may close these issues.

[Doc]: stable docs link to dev
4 participants
@tacaswell@QuLogic@jklymak@greglucas

[8]ページ先頭

©2009-2025 Movatter.jp