parse-community / parse-community/parse-dashboard
Update GitHub workflows to use latest setup-node action
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Currently we are using v1 for setting up Node.js along with manual dependency caching step.
Feature / Enhancement Description
We could upgrade the action to v2 and use built-in dependency caching:
https://github.com/actions/setup-node#caching-packages-dependencies
This would allow us to slightly simplify workflows.
Example Use Case
Alternatives / Workarounds
3rd Party References
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
Inspect the repository's GitHub workflow files and compare their setup-node usage with the linked setup-node caching documentation. Update the workflows to use setup-node v2 and its built-in dependency caching, removing the manual dependency caching steps; done means the workflows remain valid and no longer duplicate caching.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript, node.js
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100