Skip to content
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

DOC: Updating whatsnew to release 1.5.3 #50809

Merged
merged 1 commit into from Jan 18, 2023

Conversation

datapythonista
Copy link
Member

xref #49857

@datapythonista datapythonista added this to the 1.5.3 milestone Jan 18, 2023
@datapythonista datapythonista merged commit 96fc51f into pandas-dev:main Jan 18, 2023
@lumberbot-app
Copy link

lumberbot-app bot commented Jan 18, 2023

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 1.5.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 96fc51f5ec678394373e2c779ccff37ddb966e75
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #50809: DOC: Updating whatsnew to release 1.5.3'
  1. Push to a named branch:
git push YOURFORK 1.5.x:auto-backport-of-pr-50809-on-1.5.x
  1. Create a PR against branch 1.5.x, I would have named this PR:

"Backport PR #50809 on branch 1.5.x (DOC: Updating whatsnew to release 1.5.3)"

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants