Having used this action a few times now, I think there's some possibility to make the action a bit less boilerplate-y.
Specifically, if the user specifies a urlTemplate that matches ^https:\/\/github\.com\/(?<repo>.*\/.*)\/releases\/download\/, infer the following:
fromGithubReleases: true
repo: <repo from regex>
version: latest
So that this:
- uses: engineerd/configurator@v0.0.8
with:
name: "kind"
fromGitHubReleases: "true"
repo: "kubernetes-sigs/kind"
urlTemplate: "https://github.com/kubernetes-sigs/kind/releases/download/{{version}}/kind-linux-amd64"
version: "latest"
token: ${{ secrets.GITHUB_TOKEN }}
would become this:
- uses: engineerd/configurator@v0.0.8
with:
name: "kind"
urlTemplate: "https://github.com/kubernetes-sigs/kind/releases/download/{{version}}/kind-linux-amd64"
token: ${{ secrets.GITHUB_TOKEN }}
Having used this action a few times now, I think there's some possibility to make the action a bit less boilerplate-y.
Specifically, if the user specifies a
urlTemplatethat matches^https:\/\/github\.com\/(?<repo>.*\/.*)\/releases\/download\/, infer the following:So that this:
would become this: