-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install action does not honor working-directory #83
Comments
This is also a good idea. Would you like to tackle this? |
Sorry, I've moved on to working on something else and probably won't have enough spare time to tackle this. |
Got it, that's okay. |
Ran into this today too. When looking at the raw logs I don't even understand how to get it to install the .tool-versions First step list the files in the working-directory while the next step tries to install asdf and fails because it defaults to
|
You know, I just ran into this today as well. I don't suppose there's something on the roadmap to address this? Really, if I could specify a path to the .tool-versions file, that would suffice. |
hey 👋 |
The install action does not appear to honor the working-directory configured in a workflow.
In this repro project I set up, I have a
.tool-versions
file in the root that configures one version of a tool:https://github.com/mdobosz-isp/asdf-actions-wrong-dir/blob/d448ef42593a21fef79927bd5e433f2f523b3888/.tool-versions#L1
I also have a subdirectory that sets a different version of the tool:
https://github.com/mdobosz-isp/asdf-actions-wrong-dir/blob/d448ef42593a21fef79927bd5e433f2f523b3888/helm3/.tool-versions#L1
When I execute a workflow that uses the non-default working directory:
https://github.com/mdobosz-isp/asdf-actions-wrong-dir/blob/26d01bec1e7a7b48c5270acce978db41a4e2a3a4/.github/workflows/repro.yml#L22-L34
the action still appears to run in the root working directory, resulting in the wrong version being installed and invocations of the tool failing when the asdf shim tries to load the correct version.
This fails for workflows using the
v1.0.0
andmaster
versions of the action.I would expect that the
asdf install
command was executed in the appropriate working directory.The current workaround is to use the
plugins-add
action (which will also runsetup
) and runasdf install
as a freeform step.The text was updated successfully, but these errors were encountered: