docs: Forgejo as origin and the GoReleaser release flow #78
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jwarykowski/shepherd!78
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/forgejo-remote"
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?
origin is now the Forgejo repo, which runs CI and releases and push-mirrors to GitHub and Codeberg. CLAUDE.md says so in place of the old GitHub-primary line.
CONTRIBUTING's release section still said there are no GitHub Releases; it now describes the #76 flow: tag on Forgejo, wait for the mirror, GoReleaser publishes the GitHub release and the tap PR, the workflow merges it.