-
Notifications
You must be signed in to change notification settings - Fork 12
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 Test PyPI action to GitHub Publishing Workflow #99
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified lines are covered by tests ✅ 📢 Thoughts on this report? Let us know!. |
Let me know what you think of the versioning for this @falkben . Ideally, I would have liked to keep the versioning syntax that's used in the official I went with defining each version based on the date/time of the current run, which is simple. This is what a release looks like on Test PyPI: Users CAN choose to download from Test PyPI so I wonder if we should keep our version numbers the same as how we write them in PyPI. Edit: David suggests versioning with commit hash, and mentions that it can also point directly to the latest commit before the release to Test PyPI took place, so this sounds like it would be very useful. |
Closes #102
publish-to-test