inbuxa/inbuxa-webmail
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 5 Activity Sponsor

ci: copy each release to GitHub after the tag build #36

Merged
jcoffey-dev merged 1 commits from ci/github-release-copy into main 2026-09-30 13:54:42 +00:00
Conversation 0 Commits 1 Files Changed 1
+47
jcoffey-dev commented 2026-09-30 13:52:05 +00:00
Owner
Copy link
Copy source

The mirror carries tags to GitHub but not releases, so the replica's
Releases page -- and anyone watching the repository there -- stopped at the
last release made on GitHub. After the tag build has published, a new
github-release job copies the tag's Gitea release to a GitHub release: the
same notes, with PR and issue numbers rewritten to Gitea links, the same
files, and a line pointing back to the Gitea release.

It uses the run's own token and is left out of the status reported to
Gitea, so it cannot fail a release. With no Gitea release for the tag it
does nothing.

The mirror carries tags to GitHub but not releases, so the replica's Releases page -- and anyone watching the repository there -- stopped at the last release made on GitHub. After the tag build has published, a new github-release job copies the tag's Gitea release to a GitHub release: the same notes, with PR and issue numbers rewritten to Gitea links, the same files, and a line pointing back to the Gitea release. It uses the run's own token and is left out of the status reported to Gitea, so it cannot fail a release. With no Gitea release for the tag it does nothing.
jcoffey-dev added 1 commit 2026-09-30 13:52:06 +00:00
ci: copy each release to GitHub after the tag build
ci / node (pull_request) Skipped
Details
ci / version (pull_request) Skipped
Details
ci / docker-build (pull_request) Skipped
Details
ci / publish (pull_request) Skipped
Details
github/ci (branch) GitHub Actions
Details
ci / github (pull_request) Successful in 2m29s
Details
ci / announce (pull_request) Skipped
Details
a7c7d88408 
The mirror carries tags to GitHub but not releases, so the replica's
Releases page -- and anyone watching the repository there -- stopped at the
last release made on GitHub. After the tag build has published, a new
github-release job copies the tag's Gitea release to a GitHub release: the
same notes, with PR and issue numbers rewritten to Gitea links, the same
files, and a line pointing back to the Gitea release.

It uses the run's own token and is left out of the status reported to
Gitea, so it cannot fail a release. With no Gitea release for the tag it
does nothing.
jcoffey-dev merged commit b1436d4d2a into main 2026-09-30 13:54:42 +00:00
jcoffey-dev deleted branch ci/github-release-copy 2026-09-30 13:54:42 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 dependencies
Dependency updates
 documentation
Docs, README or site copy
 duplicate
Already tracked elsewhere
 enhancement
New feature or improvement
 good first issue
Good for newcomers
 help wanted
Contributions welcome
 invalid
Not a valid issue
 needs info
Waiting on the reporter for details
 question
Needs an answer, not a code change
 security
Security issue or hardening
 translation
New language or translation fixes
 wontfix
Will not be worked on
priority
p1
High priority
priority
p2
Medium priority
priority
p3
Low priority
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcoffey-dev (John Coffey)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-webmail#36