nodejs / nodejs/package-maintenance
Community maintenance of `actions/setup-node`?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
It doesn't seem like https://github.com/actions/setup-node/issues/26 will get resolved any time soon. There are other features requested (incl. PRs open) that don't seem to be getting the attention they deserve.
Should Node.js have an official action of its own?
This way we could implement the keywords support, and possibly we could recommend a different default matrix to the users.
The default matrix does have a tradeoff - right now,
a maintainer has to add new versions each time, if we recommended, say [ lts-1, lts, latest ] as the default, then the tested versions would drop off without notice, but I figure that testing in latest versions is more valuable than testing in unsupported versions, even if breaking that support means the need to bump semver major.
Related: #416
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 reviewing actions/setup-node issue #26 and related issue #416, then assess the requested keyword support and proposed default matrix. The issue does not identify files, tests, or an agreed implementation, so completion criteria would need to be established before work begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100