Hey @nyarly , we expose a variable in the github context ${{github.action_path}} that contains the path to where the action is located. You can use that in relation to your subpath to accomplish what you are trying to do if i'm understanding your use case correctly, can you try that?

There are some more docs located here

We don't support these contexts in a uses statement, which appears to be the issue here. We could support these contexts, which would allow you to do something like uses: ${{github.action_path}}/do-tedious-setup which would help this use case, but I don't think we have a dynamic way of doing this outside of your suggested workaround right now. Thanks for reporting this.

@thboop when you find the time, could you please have a look at #1684?
@nyarly, does #1684 covers your use case?

Thanks both

Running into this exact same issue right now.

I want to share common Github Actions in my org. For composite actions that use other tasks with a relative path, this breaks because it will look for the task in the consuming repository and not where the shared action is stored. I would consider this a bug.

Can this be fixed on Github's side @thboop?

Yes, when loading e.g. myaction@main, scripts called by action.yml e.g. src/myscript.py are not found during the job run.
Only scripts that are in the exact same folder side-by-side with action.yml are loaded by the job.

I wonder why this is not documented anywhere.