Allow caching without compression
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Allowing one to choose not to compress the tar archive when caching. This allows for the useful tradeoff between time and cache entry size. Note that cache size is already bounded by the total per-repo limit.
Compression frequently takes up the majority of the time spent in a cache save step, so this could offer a significant time savings at the cost of size.
This is a more specific version of #544.
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 tracing the toolkit's cache save path and reviewing the more general issue in #544 to understand the existing compression behavior. Determine where a caller could choose compression and how the cache-size limit applies; done means a cache can be saved without compression while preserving the existing compressed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100