devlooped / devlooped/dotnet-evergreen
Allow specifying a wildcard version for the updating
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 9
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Just like dotnet tool install where you can specify a wildcard like --version 42.42.42-main.*, we should also allow that so you can run an evergreen version of (say) a specific feature branch or prerelease label.
Contributor guide
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
Start by comparing the version handling with the behavior of dotnet tool install --version 42.42.42-main.*. Then trace the tool update path in this repository and determine where wildcard versions for feature branches or prerelease labels are resolved. Done means an evergreen wildcard version can be specified and updated correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100