[BUG] cocogitto-action fails in a container workflow

[joshua-clayton]

Describe the bug

Run cocogitto/cocogitto-action@v3
Run echo Installing cocogitto
Installing cocogitto
Run /home/runner/work/_actions/cocogitto/cocogitto-action/v3.9/install.sh
/__w/_temp/729ed381-bc31-4442-9f88-561d312080c8.sh: line 1: /home/runner/work/_actions/cocogitto/cocogitto-action/v3.9/install.sh: No such file or directory
Error: Process completed with exit code 127.

To Reproduce
add a "using: cocogitto-action@v3" step to a job that runs in a container: here is what I added:

Expected behavior
I expect cocogitto to run install.sh from the correct directory

Additional context
Due to what is probably a historical quirk, container workflows define $GITHUB_WORKSPACE and some other variables differently. My guess is that $GITHUB_ACTION_PATH is also defined relative to /__w/ instead of /home/runner/work.

workaround: run cocogitto-action in a non-containerized job, then pass the version to the build as an output.

[oknozor]

What container are you using ?
Can you provide the action workflow or a minimal reproducer ?

[joshua-clayton]

Hi. Those are very reasonable things to ask for. I cloned the repository, and added a container workflow test...

https://github.com/joshua-clayton/cocogitto-action/blob/container-fix/.github/workflows/ci.yaml

and while I was at it I tested out my theory and it turns out I was right. So now I've got a pull request.

#39

If you pull just the test (and not the fix) you should see it fail, and with the fix commit it passes again.