-
Notifications
You must be signed in to change notification settings - Fork 123
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
Split CI workflows into 'test' and 'deploy' #367
base: main
Are you sure you want to change the base?
Conversation
This makes them easier to maintain and follows how other pytest repositories have evolved. Also made some changes to the deploy workflow: * Using Python 3.10 * Using `build` package instead of calling `python setup.py`
f5e652d
to
e1227ad
Compare
tags: | ||
- "*" | ||
|
||
permissions: {} |
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.
Copied from pytest
im a bit unhappy with the splitting, i'd prefer if we started to install from the build artifacts for testing (like i have done for some of my projects) |
What do you mean? IIUC, you mean to test the package instead of source, but isn't that what Or do you mean to generate a single artifact, test over it, and then deploy that same artifact? |
Happy to try out something like that, can you point to a project to use as reference? |
@nicoddemus i'd love to extract this into something reusable, but currently im a bit tied up with other priorities |
This makes them easier to maintain and follows how other pytest repositories have evolved.
Also made some changes to the deploy workflow:
build
package instead of callingpython setup.py