github-action

github-action copied to clipboard

tailscale/github-action@v1 is old

4

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...

milkcocoa

notice when TAILSCALE_AUTHKEY is missing, and error early

2

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...

DentonGentry

Use Latest Version by Default

8

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....

johannesdrescher

1. not set `TAILSCALE_AUTHKEY` [ Fixes #5 ]  2. not using Linux [ Fixes #19 ] 

bxb100

It might be worth documenting that this actions currently only runs on Linux?

willnorris

It would be great to have directly typed args, instead of `args` and give an ability also to manage `tailscaled`.

XBeg9

Docs improvement: Include scopes required to authenticate the action in the readme

4

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...

bram-arcsec

Docker Build Action can't push to Tailscale-based registry

2

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...

jamie-at-arkifi

Unreliable DNS during Container Builds

13

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...

tpanum

Update README.md

2

Add required scopes

Falci