-
Notifications
You must be signed in to change notification settings - Fork 31
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
⚗️ upload to Test PyPI for pushes on main
#666
Conversation
Unfortunately, it seems that this is not really feasible. |
main
Might have found a way to make this possible after all. Investigating further. |
ed7497d
to
6983abb
Compare
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
6983abb
to
0254d77
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #666 +/- ##
=====================================
Coverage 92.1% 92.1%
=====================================
Files 125 125
Lines 13757 13757
Branches 2150 2150
=====================================
+ Hits 12671 12672 +1
+ Misses 1086 1085 -1
|
## Description A small follow-up PR to #666 that adjusts how the continuous deployment job is run. Hopefully, after merging, this allows to continuously upload to TestPyPI. ## Checklist: <!--- This checklist serves as a reminder of a couple of things that ensure your pull request will be merged swiftly. --> - [x] The pull request only contains commits that are related to it. - [x] I have added appropriate tests and documentation. - [x] I have made sure that all CI jobs on GitHub pass. - [x] The pull request introduces no new warnings and follows the project's style guidelines. Signed-off-by: burgholzer <burgholzer@me.com>
Description
This PR updates the CD workflow so that anytime it runs on a push to
main
, it uploads the resulting package to Test PyPI. This allows to battle test the packages before official releases.This will be especially important in the context of #662.
Checklist: