magerbeton/tea - tea - Gitea: Git with a cup of tea

4 Commits

Author	SHA1	Message	Date
magerbeton	12c0603966	ci: drop actions/upload-artifact, tolerate existing releases release / release (push) Canceled after 27h55m13s Details upload-artifact@v4 talks to GitHub's artifact service and times out on Gitea. Distribution happens via release assets anyway. Also reuse an existing release for a tag instead of failing on a 409.	2026-08-23 17:05:03 +02:00
magerbeton	df6e626533	ci: drop upstream goreleaser workflows The fork uses its own release.yml (plain go build + Gitea release) and does not have the goreleaser-pro, R2/S3 and GPG secrets the upstream release workflows require.	2026-08-23 16:39:34 +02:00
magerbeton	3ef1e5626f	ci: add multi-platform release build via Gitea Actions goreleaser / goreleaser (push) Failing after 10s Details goreleaser / goreleaser (push) Failing after 10s Details goreleaser / release-image (push) Failing after 4m53s Details goreleaser / release-image (push) Failing after 4m43s Details release / release (push) Failing after 9m1s Details Builds tea for linux/amd64, linux/arm64, darwin/amd64, darwin/arm64 and windows/amd64 on tag push and publishes them as a Gitea release.	2026-08-23 16:37:59 +02:00
magerbeton	e0bdf2f57b	fix(git): tolerate remotes without a url key goreleaser / goreleaser (push) Failing after 1m9s Details goreleaser / release-image (push) Failing after 2m46s Details goreleaser / goreleaser (push) Canceled after 1s Details goreleaser / release-image (push) Failing after 14s Details git-annex S3 special remotes have no url key; running `git config --get-all remote.<name>.url` on them exits 1, which made tea hard-fail in Config() on any repo that has such a remote. Treat a missing key (exit 1 with empty or 'No such section or key' stderr) as an empty URL list, mirroring the existing branch-section handling.	2026-08-23 16:07:55 +02:00