tailscale / tailscale/go-cache-plugin
Ongoing maintenance / moduleIndex entry skipping
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 81
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I'm working on a change for this tool that will allow for skipping uploads for moduleIndex entries (they are lightweight and depend on file mtime, which thrashes run-to-run for us, so they never get reused). I wanted to check in here real quick to see if there are plans to maintain this ongoing (in which case I'll open an upstream PR), or if I should just fork the repo to my company's org and work there in an ongoing fashion. No big deal either way, just want to know before I deal with rewriting module paths, etc.
Thanks!
Contributor guide
No contributing guide indexed for this repository
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 locating the moduleIndex handling and the upload path, then review how module paths and file mtimes determine cache reuse. Done would mean an agreed upstream approach for skipping uploads of moduleIndex entries and confirmation that the behavior works across repeated runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100