github-action
github-action copied to clipboard
A GitHub Action to connect your workflow to your Tailscale network.
I use this action with `@v1` as follows. ``` - uses: tailscale/github-action@v1 with: authkey: ${{ secrets.TAILSCALE_AUTHKEY }} ``` GitHub actions runner seems to use the old tailscale 1.14 version. Is...
When a pull request is initiated from a fork, none of the secrets of the original repo are available. This notably includes the TAILSCALE_AUTHKEY, which means tailscaled in the CI...
Instead of hard coding a default version, why not use the latest version by default? This would make the action simpler to use and reduce the need for future maintenance....
1. not set `TAILSCALE_AUTHKEY` [ Fixes #5 ] ![image](https://user-images.githubusercontent.com/20685961/150722378-47ccb144-901e-41e7-bf80-deac7b4ec57a.png) 2. not using Linux [ Fixes #19 ] ![image](https://user-images.githubusercontent.com/20685961/150722444-e71a5007-c869-4c22-a6e4-7a28ca2074a6.png)
It might be worth documenting that this actions currently only runs on Linux?
It would be great to have directly typed args, instead of `args` and give an ability also to manage `tailscaled`.
The README recommends the use of the OAuth API to register the client. There seems to be no fine grained permissions to limit the usage of the OAuth credentials to...
I strung together a github actions job with the steps: 1. `tailscale/github-action` 2. `docker/setup-qemu-action` 3. `sigstore/cosign-install` 4. `docker/setup-buildx-action` 5. `actions/checkout` 6. `docker/metadata-action` 7. `docker/build-push-action` (2-7 are pretty much default multi-platform...
I have a GitHub Actions pipeline that roughly process like so: 1) Connect to a private Tailscale network using this Github Action. 2) Start a docker build of a multi-stage...
Add required scopes