cirruslabs / cirruslabs/cirrus-cli
Cache cleanup strategy based on overall cache size
Open
enhancement
good first issue
help wanted
- Dominant language
- Go
- Stars
- 285
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Related to #17
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading related issue #17, since this issue provides no implementation or test location. Clarify the intended cache-size policy and identify the relevant cache-management entry point before estimating the work. Done should mean cleanup behavior is driven by the overall cache size.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100