You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why does this action fail is there isn't any .tool-versions file?
That's' not how asdf install behaves on my local computer.
There it falls back to check in my home directory for ~/.tool-versions (which this action doesn't seem to do?).
And even then if it isn't there, it doesn't fail, right?
I'd like to use this for a reusable workflow in my organization, where we can "install things from asdf if the repository is using a .tool-versions file, otherwise not".
Today, running this action without a .tool-versions file in the current directory, the action fails with: Action failed with error Error: ENOENT: no such file or directory, open '.tool-versions'
The text was updated successfully, but these errors were encountered:
Why does this action fail is there isn't any
.tool-versions
file?That's' not how
asdf install
behaves on my local computer.There it falls back to check in my home directory for
~/.tool-versions
(which this action doesn't seem to do?).And even then if it isn't there, it doesn't fail, right?
I'd like to use this for a reusable workflow in my organization, where we can "install things from asdf if the repository is using a
.tool-versions
file, otherwise not".Today, running this action without a
.tool-versions
file in the current directory, the action fails with:Action failed with error Error: ENOENT: no such file or directory, open '.tool-versions'
The text was updated successfully, but these errors were encountered: