Use @actions/tool-cache

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, javascript
Domain
ci-cd

Research direction

Start with the linked @actions/tool-cache package and inspect the repository’s current composite GitHub Action entry points. Completion means using tool-cache in the planned JavaScript action after the composite-action transition; the issue names no files or tests, so the implementation scope needs clarification.

Written by the indexing model from the issue text.

Description

See https://github.com/actions/toolkit/tree/main/packages/tool-cache

This is relevant when we switch this over to a proper JavaScript action as opposed to a composite action.

Dominant language
Shell
Stars
29
Forks
19
Avg merge
3m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/setup-cli

All issues in databricks/setup-cli

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.