| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I've tested this here: https://github.com/patrick91/test-action-poetry-cache/runs/4341929604?check_suite_focus=true |
Sorry, something went wrong.
|
Great improvement! |
Sorry, something went wrong.
|
Keep going! :) |
Sorry, something went wrong.
|
Any update on this? |
Sorry, something went wrong.
I've rebased the PR, but we have to wait the mainteners to review the PR. They are probably busy with other priorities so we'll probably have to wait a bit 😊 |
Sorry, something went wrong.
|
Could you please sync with the main branch ? |
Sorry, something went wrong.
|
I closed this by mistake :) @dmitry-shibanov the PR should be up to date now! |
Sorry, something went wrong.
|
Hello @patrick91. Could you please run these commands:
|
Sorry, something went wrong.
|
Not 100% sure why the CI failied, I'll try to take a look soon, maybe a rebase helps 😊 |
Sorry, something went wrong.
|
Rebased this again :) |
Sorry, something went wrong.
|
Super stoked for this! Keep the good work up @patrick91 💘 |
Sorry, something went wrong.
|
Friendly bump here, can a maintainer at least approve the CI workflows so the submitter can see if everything's still passing?
|
Sorry, something went wrong.
|
@dmitry-shibanov pipenv seems to fail on main too, shall I sent a PR to try and fix that? Also I did rebase and ran npm run build && npm run format, but the check is still failing 🤔 |
Sorry, something went wrong.
|
@patrick91 I looked at that failure briefly but couldn't figure it out. If you know what the issue is and want to submit a separate PR, that would be great. Otherwise, we don't need to block this on that. What you do need to fix is the check-dist failure. You can just download the artifact from that run and check it in. |
Sorry, something went wrong.
Co-authored-by: Brian Cristante <33549821+brcrista@users.noreply.github.com>
There was a problem hiding this comment.
Thank you @patrick91!
Sorry, something went wrong.
|
nice work |
Sorry, something went wrong.
As of yesterday, `@actions/setup-python@v3` supports this via v3.1.0: [Release](https://github.com/actions/setup-python/releases/tag/v3.1.0), [Tag](https://github.com/actions/setup-python/tree/v3.1.0), actions/setup-python#281 ```yaml steps: - uses: actions/checkout@v3 - name: Install poetry run: pipx install poetry - uses: actions/setup-python@v3 with: python-version: '3.9' cache: 'poetry' - run: poetry install - run: poetry run pytest ``` See also: python-poetry/poetry#4205
…ython@v3 poetry install will pick up the python binary at the time it was installed (before actions/python ran) so it looks like poetry env needs to be set manually. https://github.com/actions/setup-python/releases/tag/v3.1.0 https://github.com/actions/setup-python/tree/v3.1.0 actions/setup-python#281
Add poetry caching support
| Back | FazBrowse Home | New Git URL |
Description:
A continuation of #266 to add support for caching poetry's virtualenv
This is still draft, I need to implement the actual caching, but it is good to start running the tests early :)
Check list: