ci: gitea publishes Harbor on tag, github does the rest

[ashish1099]

What

Splits release responsibilities now that origin points at GitHub and Gitea is a mirror:

	Gitea	GitHub
Tests / lint / fmt	removed	.github/workflows/test.yml
Container image	harbor.obmondo.com/obmondo/gfetch	ghcr.io/obmondo/gfetch
Binaries + release notes	removed	GoReleaser in .github/workflows/release.yml
Trigger	v* tag only	v* tag (release), push/PR (CI)

Gitea keeps exactly one job — the Harbor push, which GitHub cannot do — and nothing else.

Why the release workflows also needed fixing

d4c49bf ("unify build and release process with goreleaser") moved image building out of
docker/build-push-action and into GoReleaser's dockers: block. That cannot work here:
GoReleaser builds images in a temp directory containing only the compiled binaries plus the
Dockerfile, but our Dockerfile builds from source (COPY go.mod go.sum ./ then go build).
go.mod is not in that context, so the build fails before it starts.

It went unnoticed because no release workflow has ever run — GitHub Actions history shows only
Tests and CodeQL, zero goreleaser runs. The image currently published at
ghcr.io/obmondo/gfetch:v1.2.0 was built by the old docker.yml that d4c49bf deleted.

So image building returns to docker/build-push-action with full repo context, and GoReleaser goes
back to what it does well: binaries, archives, changelog, GitHub release.

Bugs fixed along the way

• Gitea had no Harbor login. The "Login to Harbor" step invoked setup-go, not
  docker/login-action — a copy-paste slip, so no authentication happened at all.
• GitHub had no registry login whatsoever, while .goreleaser-github.yaml had push: true to
  ghcr.io.
• Malformed GHCR image name. ghcr.io/{{.Env.GITHUB_REPOSITORY}}/gfetch resolves to
  ghcr.io/Obmondo/gfetch/gfetch — a doubled path segment, and uppercase, which GHCR rejects.
  Verified against the registry: ghcr.io/obmondo/gfetch:v1.2.0 returns 200, the doubled name 403s.
• No QEMU/buildx setup in either workflow, despite both declaring
  --platform=linux/amd64,linux/arm64. (An abandoned checkpoint branch in this repo carries the
  matching buildx failed ... failed to solve error.)

Judgement call worth a look

.goreleaser-gitea.yaml is deleted. With GoReleaser no longer running on Gitea it is dead
config — but it also means no more Gitea releases or binary archives; Harbor becomes the only
artifact Gitea produces. That follows "only the tags push for gitea and nothing else", but it is one
revert away if you want Gitea releases kept.

Before this actually works

• Gitea needs HARBOR_USERNAME / HARBOR_PASSWORD secrets, and the obmondo project must exist in
  Harbor. I could not verify either from here.
• The Gitea mirror must receive tags. It is currently 3 commits behind and pushes now go only to
  GitHub — if EnableIT/gfetch is not configured as a Gitea pull-mirror, the tag never lands there
  and the Harbor job never fires.
• CodeQL is GitHub "default setup" (repo settings, not a workflow file), so it stays on GitHub
  automatically — nothing to change.

Not run: go build / tests, per your usual preference. YAML of all workflows was parse-checked.

🤖 Generated with Claude Code