Install dependencies via pixi and run the tests #7
Conversation
|
Review these changes at https://app.gitnotebooks.com/stumpy-dev/automate/pull/7 |
Stumpy actions with pixi
add my own secret and enable environment in Github Actions
add check token
attemp2 in token authentication
set cache to false
keep core stuff
NimaSarajpoor
force-pushed
the
stumpy_actions_with_pixi
branch
from
0976d65 to
f869860
Compare
NimaSarajpoor
force-pushed
the
stumpy_actions_with_pixi
branch
from
412afe3 to
b0c848d
Compare
Stumpy actions with pixi
potential fix for missing env
|
@seanlaw I've generated API Key from my account in prefix.dev and saved it in a secret, and used it in the yml file. See Github Actions Run in the forked repo. |
| os: [ubuntu-latest, macos-latest, windows-latest] | ||
| environment: PIXI_API_ACCESS | ||
|
|
||
| steps: |
There was a problem hiding this comment.
Add support for different versions of python. To get range of python versions, see:
There was a problem hiding this comment.
I would just leave it as "latest" Python instead of looking at a range. We'll run a test every day but, realistically, using pixi is only for developers.
It looks like this is to check pixi only (based on the workflow name). I think pixi-actions.yml as a workflow name is fine. Will you be creating a separate workflow for fftw later? I hope so :)
|
@NimaSarajpoor When I go to: Settings > Secrets and Variables > Actions It states:
So, I believe that the workflow needs to be merged first before it can have access to the token |
| repository: stumpy-dev/stumpy | ||
|
|
||
| - name: Set Up Pixi | ||
| uses: prefix-dev/setup-pixi@v0.9.4 |
There was a problem hiding this comment.
Do we need to be so specific about the version? Is there a way to simply use the latest version for both the setup as well as the pixi-version?
2 participants
No description provided.