Publish the .proto files for the new cache service
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
My company has a project, Magic Nix Cache, that uses the GitHub Actions cache API to serve as a Nix binary cache in CI.
Given the new cache backend and the sunsetting of the old one, I'm looking to update a project that uses the v1 api directly. It looks like the .proto files are not checked in to this repo, and only the generated code is present.
Are these proto files intentionally excluded? If so, Magic Nix Cache is going to break suddenly and be very challenging to make work again. That would be unfortunate, because it gives Nix users a no/low-cost binary cache for small projects' CI, using just the GitHub Actions primitives.
Please consider publishing the proto files.
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
Locate the generated cache-service code and the source-generation or packaging entry point for the v1 cache API. Publish the corresponding .proto files in the repository so projects using the API can obtain the schemas directly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100