Hi there!
It would be neat, if goreleaser-action could tell goreleaser the GitHub API URL by extracting them / building them from the GitHub event context.
The github.api_url context already lists the required API URL directly - https://docs.github.com/en/actions/reference/workflows-and-actions/contexts#github-context, so it would "just" require passing it into the running goreleaser process, still allowing it to be overridden by the goreleaser.yaml. From that the upload URL could then be found automatically - see https://github.com/orgs/goreleaser/discussions/6274
I think it would be beneficial to have goreleaser work automatically no matter the GitHub instance being used - be it github.com or a GHES instance inside a company. This would make it easier for people having to rebuild source locally, since they do not need adjust the upstream goreleaser config if the config is written in a way to work seamlessly across forks (e.g. by using env vars to refer to the repo owner)
Hi there!
It would be neat, if goreleaser-action could tell goreleaser the GitHub API URL by extracting them / building them from the GitHub event context.
The
github.api_urlcontext already lists the required API URL directly - https://docs.github.com/en/actions/reference/workflows-and-actions/contexts#github-context, so it would "just" require passing it into the running goreleaser process, still allowing it to be overridden by the goreleaser.yaml. From that the upload URL could then be found automatically - see https://github.com/orgs/goreleaser/discussions/6274I think it would be beneficial to have goreleaser work automatically no matter the GitHub instance being used - be it github.com or a GHES instance inside a company. This would make it easier for people having to rebuild source locally, since they do not need adjust the upstream goreleaser config if the config is written in a way to work seamlessly across forks (e.g. by using env vars to refer to the repo owner)