Support asdf `.tool-versions` File

Open
#459 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 7 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
devops, tooling

Research direction

The issue names no repository files, tests, or entry points. Read the .tool-versions format and compare the linked setup actions first; done means setup-dotnet consistently reads the file for its runtime version and has coverage for that behavior.

Written by the indexing model from the issue text.

Description

feature request needs eyes

Description:
actions/setup-node, actions/setup-python, ruby/setup-ruby, and erlef/setup-beam all support reading from .tool-versions. It would be helpful to have such support consistently in all official setup actions.

Justification:
With over 18k stars and over 400 plugins, asdf is the most popular multi-language runtime manager. .tool-versions is becoming the de facto standard for pinning runtimes, package managers, and other development tools as most other standardized file formats support only one tool.

Are you willing to submit a PR?
No

Dominant language
TypeScript
Stars
1.2k
Forks
579
Avg merge
6d 4h
Merged PRs (30d)
1

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/setup-dotnet

All issues in actions/setup-dotnet

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.