Split CI workflows into 'test' and 'deploy'#367
Conversation
nicoddemus
changed the title
nicoddemus
force-pushed
the
split-workflows
branch
from
f5e652d to
e1227ad
Compare
| tags: | ||
| - "*" | ||
|
|
||
| permissions: {} |
|
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.
Not needed, improves security.
As suggested by zizmor. https://docs.zizmor.sh/audits/#dependabot-cooldown
Fix https://docs.zizmor.sh/audits/#unpinned-uses. Used `uvx gha-update`: https://github.com/davidism/gha-update
Not actually vulnerable, but better use the safe pattern anyway. https://docs.zizmor.sh/audits/#template-injection
|
Rebased and also brought over some other improvements from pytest, and some zizmor fixes. |
3 participants
This makes them easier to maintain and follows how other pytest repositories have evolved.
Also made some changes to the deploy workflow:
buildpackage instead of callingpython setup.py