azy5030
c9a31ba468
- ci.yaml: filter the push trigger to branches. An unfiltered `push` also fired for every tag ref, including the vendor-release tags the bump script creates via the API. - bump-version.sh: remove the pkgcheck/emerge/--version validation before push. The branch push triggers CI, which runs the same checks and, unlike the script's local copy, fetches the real release asset. The PR body now asks for green CI instead of claiming the build passed in the bump job. - vendor-tags.yaml: new workflow on pushes to master touching dev-util/**. The vendor release is created before the bump commit exists (and PRs are squash-merged), so its tag pointed at an arbitrary master commit. This force-updates each vendor tag whose ebuild is in the tree to the master commit that added that ebuild. Tags are only ever updated, never deleted, since deleting a release's tag deletes the release and its assets. - CLAUDE.md: document both changes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
azy5030 overlay
A personal Gentoo ebuild repository (overlay) for packages not in the main ::gentoo tree.
Packages
| Package | Description |
|---|---|
dev-util/gitea-runner |
Gitea Actions runner (formerly act_runner), built from upstream source with a vendored Go module tree. |
Using the overlay
eselect repository add azy5030 git https://git.azy.dev/azy5030/azy5030-overlay.git
emaint sync -r azy5030
echo 'dev-util/gitea-runner ~amd64' >> /etc/portage/package.accept_keywords/gitea-runner
emerge dev-util/gitea-runner
Maintenance
.gitea/workflows/ci.yamlbuilds each package in agentoo/stage3container on every push and asserts the resulting binary runs..gitea/workflows/bump.yamlrunsscripts/bump-version.shdaily: it checks the upstream releases feed and, when a newer version exists, regenerates + uploads the vendor tarball, bumps the ebuild, and opens a pull request. Requires aBUMP_TOKENrepository secret (scopes: repository read/write, write release).