chore(org): retarget release workflow to RunicGateway/link #9
Reference in New Issue
Block a user
No description provided.
Delete Branch "chore/org-rename-runicgateway"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to the
UOM→RunicGatewayGitea org transfer (repo reorg Phase 1).What changed
.gitea/workflows/release.yml—REPO: UOM/link→RunicGateway/link(and the matching comment).Why it matters
REPOdrives two things in the release job:https://…@${GITEA_HOST}/${REPO}.git), and/api/v1/repos/${REPO}/releases).Left as
UOM/link, the next release would push and create releases against the old org path (working only as long as Gitea's transfer redirect holds). This points it at the current repo.No functional/build logic touched — env var only.
🤖 Generated with Claude Code