@nilason it seems better, but it can't find the Python grass package.

Starting at :
https://github.com/OSGeo/grass/actions/runs/13319730333/job/37201916826#step:7:9302

It seems to me we need to run Docker in PR.

It seems to me we need to run Docker in PR.

In general we still have too much total CI time. With little more than occasional activity, the CIs get bogged down quickly and prevents further work. Which is a shame.
Would it be possible to trigger a workflow based on changes on any Dockerfile (modified file by name)?

It seems to me we need to run Docker in PR.

In general we still have too much total CI time. With little more than occasional activity, the CIs get bogged down quickly and prevents further work. Which is a shame.

Would it be possible to trigger a workflow based on changes on any Dockerfile (modified file by name)?

Once the workflow itself is verified safe to run on PRs, then it would be possible to use a similar approach to the one used in additional checks, like for pre-commit. We could also add a workflow_dispatch trigger, that means we can manually launch a run.

workflow_dispatch would perhaps be the least complicated solution.

And that would also be available if there are other changes that are not in Dockerfile but potentially still affect.

workflow_dispatch would perhaps be the least complicated solution.

But, would be needed to run on the fork's branch, because I don't think we can select a branch to run on on a branch that comes from a forked repo (like all our PRs come from forks)

And that would also be available if there are other changes that are not in Dockerfile but potentially still affect.

For this, I only know that there's a way to do something that works with custom-purpose labels to control what to run/request what to run. But it's harder to setup, but afterwards it's kind of easy to use