actions / actions/starter-workflows
> But there is no standards way of describing the version of the program being installed
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.1k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Description
> But there is no standard way of describing the version of the program being installed
Since go 1.16, you can use go install module@version and go run module@version to specify the version.
Originally posted by @silverwind in https://github.com/actions/setup-go/issues/483#issuecomment-2196622115
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
No file, test, or specific workflow is named. Start by reviewing the Go-related workflow templates in actions/starter-workflows and the linked setup-go discussion to determine the intended change; completion criteria are not defined in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100