actions / actions/setup-dotnet
Support asdf `.tool-versions` File
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 572
- Avg merge
- 12d 20h
- Merged PRs (30d)
- 1
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- typescript
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100