-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Updated release instructions to use rst instead of markdown #50886
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
Updated release instructions to use rst instead of markdown #50886
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this @tpackard1. Looks great, only one minor comment that I think will make the next comment easier to understand (I was a bit confused first).
Open a PR updating the build commit to the released version, and merge it once the | ||
CI is green. | ||
CI is green to do this type:: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI is green to do this type:: | |
CI is green. To do this type:: |
6a54502
to
ecd3212
Compare
- Permissions to push to main in the pandas repository, to push the new tags. | ||
- Write permissions to [PyPI](https://github.com/conda-forge/pandas-feedstock/pulls) | ||
- Write permissions to `PyPI <https://github.com/conda-forge/pandas-feedstock/pulls>`_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Write permissions to `PyPI <https://github.com/conda-forge/pandas-feedstock/pulls>`_ | |
- `Write permissions to PyPI <https://github.com/conda-forge/pandas-feedstock/pulls>`_ |
To avoid
2023-01-20T05:53:13.6374953Z /home/runner/work/pandas/pandas/doc/source/development/maintaining.rst:5: WARNING: Duplicate explicit target name: "pypi".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mroeschke! I will make the change rn
Thanks @tpackard1 |
…ev#50886) * rst formatted release instructions * updated release instructions line 456 * avoid duplicate explicit target name
@datapythonista I tried to fix the other pull request but made a mess of it so I thought it would be best to start over. If this was the wrong, please let me know what should have been done; still learning the GitHub/ git workflow.