-
Notifications
You must be signed in to change notification settings - Fork 933
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
Add a guide about publishing dists via GH Actions #647
Add a guide about publishing dists via GH Actions #647
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.
Looks good, some minor suggestions.
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
Co-Authored-By: Hugo van Kemenade <hugovk@users.noreply.github.com>
Folks, this is ready for a new round of reviews. I've factored out the workflow sample into a separate file and addressed all the major concerns. |
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.
Looks good, just a few more minor bits!
. | ||
# Actualy publish to PyPIs | ||
- name: Publish 📦 to Test PyPI | ||
uses: pypa/gh-action-pypi-publish@master |
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.
Once there's a release, include the version number here.
We strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag number. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update.
- Using the commit SHA of a released action version is the safest for stability and security.
- Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work.
- Using the
master
branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break.
https://help.github.com/en/articles/workflow-syntax-for-github-actions#jobsjob_idstepsuses
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.
Sure, I'd also mention it somewhere in the README of the action itself.
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
Co-Authored-By: Hugo van Kemenade <hugovk@users.noreply.github.com>
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.
This looks pretty good.
I'm not 100% sure that we should advise users to publish to TestPyPI on every push, but I think it's probably OK.
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/github-actions-ci-cd-sample/publish-to-test-pypi.yml
Outdated
Show resolved
Hide resolved
source/guides/github-actions-ci-cd-sample/publish-to-test-pypi.yml
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst
Outdated
Show resolved
Hide resolved
Co-Authored-By: Dustin Ingram <di@users.noreply.github.com>
Co-Authored-By: Dustin Ingram <di@users.noreply.github.com>
Co-Authored-By: Dustin Ingram <di@users.noreply.github.com>
@di would you please take a look? |
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.
I think this is good-enough to publish now; we can always iterate and improve this as we go.
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.
Concur with @pradyunsg here - I think there are some interesting questions on specifics in the remaining comments, but I also think they can be tackled via a follow-up PR.
Thanks, Nick! I'm also aware of other problems that need to be addressed and I'm going to solve those too, in the follow-up PRs. |
Resolves pypa/gh-action-pypi-publish#2