2 Commits

Include renames

Author	SHA1	Message	Date
jared	9617b86a26	ci: mirror canonical tag objects, not the lightweight refs checkout builds ... v0.4.0 failed to mirror, and it would have failed at every future release. On a tag-triggered run, checkout materializes refs/tags/<tag> as a LIGHTWEIGHT tag at the commit SHA; the annotated tag object Gitea holds is never fetched. Run 2070 therefore pushed a lightweight v0.4.0 to GitHub and reported success. Run 2076, on main with fetch-depth 0, did fetch the real annotated object and was rejected with "already exists" trying to correct it -- git will not clobber an existing tag. Gitea had e138eeb (annotated), GitHub had d2caa6d (the commit). Re-fetch canonical tag objects from Gitea before pushing. --force rewrites LOCAL tag refs only; it is not a force push and does not weaken the non-force guarantee on main. It is required: without it the fetch is rejected with "would clobber existing tag" and the lightweight ref survives to be mirrored again. Verified against a scratch clone -- lightweight d2caa6d becomes annotated e138eeb, peeling back to the same commit; without --force the tag is unchanged. The GitHub tag was repaired by hand out of band, so the two remotes already agree; this stops it recurring.	2026-08-11 09:57:14 -04:00
jared	28c500f47a	ci: mirror main and tags to the GitHub mirror ... A plain non-force git push rather than Gitea's built-in push mirror. A push mirror force-updates the refs it owns, so a Merge clicked on a GitHub PR would be silently overwritten on the next sync -- the PR still reading 'Merged' while its commit became unreachable. A non-force push is rejected instead, which turns that into a red CI run. Secret is PAT_GH, not GITHUB_MIRROR_PAT: Gitea reserves the GITHUB_ and GITEA_ prefixes for its own injected variables and refuses secrets using them.	2026-08-08 20:20:56 -04:00