tailscale / tailscale/github-action
Feature: Cache Tailscale credentials
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 938
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Description
When tailscale's systems are having an outage, this causes an immediete disruption to anyone using this action to get their CI on their tailnet.
This action can cache the credentials used in the past (possibly with a user defined cache key so we don't have workflows using each others credentials). If the credentials are still valid, then we would remove a strong dependency on the coordination server.
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
No files, tests, or entry points are named. Locate the TypeScript action entry point and trace how credentials are obtained and used; then clarify the cache boundary, user-defined key behavior, and credential-validity check. Done means valid cached credentials can let workflows continue during a Tailscale coordination outage without mixing credentials between workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100