Skip to content

Support custom paths for .tool-versions #586

Open
@DimitriosNaikopoulos

Description

@DimitriosNaikopoulos

What do you think about supporting a GHA option to use a different file than the default .tool-versions ?

Example:

...
steps:
  - uses: action/checkout@v4
  - uses: asdf-vm/actions/install@v2
     with:
        tool-versions-path: ./my/custom/path/.tool-versions 

or

...
steps:
  - uses: action/checkout@v4
  - uses: asdf-vm/actions/install@v2
     with:
        tool-versions-path: ./.tool-versions.ci

This will allow users to manage tools differently in CI to avoid installing unnecessary development dependencies that someone may only need on their local machine.

Do you think that could be possible?

Thanks 😄

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions