Impossible to use for Python-based actions

[hynek]

I've been using pdm for a while to manage the deps for my build-and-inspect-python-package but kept exporting to an requirements.txt. But after running into some issues with pdm export I've decided to try to switch to pdm wholesale, but that doesn't seem to be possible, because pdm instantly looks for a pdm.lock and fails if it doesn't find it: https://github.com/hynek/build-and-inspect-python-package/actions/runs/5636001548/job/15267605972

You have more experience writing GitHub Actions so maybe I'm missing something? It seems to me tho, that I'd need an project-path input to be able to point the action to ${{ github.action_path }}?

[frostming]

It looks for lockfile as the cache key when cache is true, try turning off the caches.

[hynek]

You're referring to the secondary problem, correct? I got that solved in Discord, but unless I want to export my lock files manually or rebuild a secondary PR workflow around the exported file, I need a way to tell pdm where to look for the project.

[frostming]

Okay, so what problems are left, exporting issue or changing directory?

[hynek]

Sorry for mixing this two. I have both problems and they block me from using PDM for an GitHub Action.

The primary here is, that it's impossible to use setup-pdm when the Python project I'm about to use is not in the current directory (but in this case ${{ github.action_path }}).

I'm basically trying to migrate everything into PDM instead of doing exports: hynek/build-and-inspect-python-package#57

I can't be 100% sure that will work out, but currently I'm blocked on this.

[hynek]

We have fixed this problem on Discord: my failure is only caused by the caching implemention. The solution is to either disable it or point it to the file.