Automatically store fork cache on github

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, javascript
Domain
ci-cd, devops

Research direction

Start by reading the GitHub Action's existing setup and dependency-cache configuration, then compare its behavior with the referenced Scarb action cache. Identify where a rerun on the same project could restore and save the fork cache; done means the cache is reused automatically without requiring additional user configuration.

Written by the indexing model from the issue text.

Description

The action should be able to store the fork cache automatically, if it is being rerun on the same project. Similarly to how scarb action caches it's dependencies.

Dominant language
JavaScript
Stars
14
Forks
5
PR merge metrics
No merged PRs in 30d

Getting set up

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 foundry-rs/setup-snfoundry

All issues in foundry-rs/setup-snfoundry

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.