Skip to content

Conversation

borchero
Copy link

@borchero borchero commented May 1, 2024

Motivation

Potentially, tailscale(d?) have been installed via a separate workflow step to manage the Tailscale version via an external tool (e.g. via conda-forge - tailscale, tailscaled). This change allows tailscale/github-action action to simply use these installed binaries rather than forcing the user to download additional binaries.

@borchero
Copy link
Author

borchero commented May 3, 2024

I just noticed that this would also solve #56 (and supersede #103) as brew install tailscale can be run in a separate step.

@borchero
Copy link
Author

borchero commented May 4, 2024

FYI, I tested the latest commit in a personal project and it worked nicely.

@jayvdb
Copy link
Contributor

jayvdb commented Jun 8, 2024

@borchero , could you rebase this

@borchero
Copy link
Author

@jayvdb sorry for the delay, finally done 😄

@borchero borchero requested a review from jayvdb June 17, 2024 20:10
@jayvdb
Copy link
Contributor

jayvdb commented Jul 29, 2024

ping @knyar & @patrickod & @willnorris

@haron
Copy link

haron commented Mar 17, 2025

bump, just in case

@borchero
Copy link
Author

I'm not really sure what to do to link an already present binary on Windows -- do I need to do anything if it's on the path?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants