Inquiry about publishing Homebrew tap from private GitLab CI to public GitHub repository at ORG level

[Noush-012]

Hi

Thank you so much for the wonderful project !!!
I'm curious if anyone has successfully set up a workflow to publish Homebrew taps from a GitLab CI pipeline to a GitHub repository.

Specifically, I'm interested in understanding:

Whether it's feasible to publish Homebrew taps directly from a GitLab CI pipeline to a GitHub repository?
Any potential challenges or best practices in accomplishing this integration?
Any existing workflows or examples that demonstrate this setup?
Any insights, tips, or pointers to relevant resources would be greatly appreciated. Thank you in advance for your help!

[caarlos0]

Thanks!

Currently goreleaser uses whatever is available (e.g. if GITHUB_TOKEN is set, it'll push everything to github), maybe we should allow to set a "provider" or something like that

In the meantime, it might be possible if you push to git directly instead of using the APIs, e.g.

brews:
  - ...: ...
    repository:
      owner: foo
      name: bar
      git:
        url: 'ssh://[email protected]:foo/bar.git'
        private_key: '{{ .Env.PRIVATE_KEY_PATH }}'

PS: I haven't test this particular scenario

[Noush-012]

Since there is only one SCM allowed for one configuration, I thought of using another pipeline job that only takes care of the GitHub token forcefuly and publishes the Brew formula while skipping the upload to the SCM. please your thoughts?

.goreleaser-brew.yml

  # Homebrew tap
version: 1
project_name: helloworld

builds:
  - main: ./cmd/server/main.go
    goos:
      - darwin
      - linux
    goarch:
      - amd64
      - arm64
    env:
      - CGO_ENABLED=0
    flags:
      - -mod=vendor

universal_binaries:
  - replace: true
force_token: github
release:
 skip_upload: true

brews:
  - name: helloworld
    description: "helloworld program."
    repository:
      owner: foo
      name: bar

[Noush-012]

oh !!
even if set,

release:
 skip_upload: true

⨯ release failed after 8s                  error=scm releases: failed to publish artifacts: could not release: POST https://api.github.com/repos/npm/helloworld/releases: 404 Not Found []
Cleaning up project directory and file based variables

[caarlos0]

skip upload skips the upload, not the release creation itself

you might want to set release.disable.