-
Notifications
You must be signed in to change notification settings - Fork 44
Adds workflow to upload to test.pypi #565
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
Conversation
This is a workflow to help the release managers to get accustomed with the release process. This gives us the ability to run tests without messing the real PyPI.
If I'm understanding correctly (I quickly skimmed the PR), these "test builds" still seem to interact with the real repository and create commits and tags on the main branch, but then they're not actually published to PyPI. That seems problematic to me.
If I'm understanding correctly (I quickly skimmed the PR), these "test builds" still seem to interact with the real repository and create commits and tags on the main branch, but then they're not actually published to PyPI. That seems problematic to me.
Updated both the PR description to mark that this has to run on maintainer's fork, and also updated the workflow name. But even for test PyPI the maintainer has to first get access to test-pypi maintainer's group so that they can their repositories as trusted publisher.
Updated both the PR description to mark that this has to run on maintainer's fork
Would be great to make it fail early if it's run in this repo instead of a fork.
@anweshadas how/when do you plan to continue with this?
@anweshadas how/when do you plan to continue with this?
I will work on it sooner, since we will be needing this for the mentees.
Uh oh!
There was an error while loading. Please reload this page.
This is a workflow to help the release managers to get accustomed with the release process.
This gives us the ability to run tests without messing the real PyPI.
This workflow needs to run on the maintainer's fork so that it does not pollute the upstream repository.