From 273862c882b117308e02d92408e513056ede95fa Mon Sep 17 00:00:00 2001 From: Skyler Lehmkuhl Date: Sun, 21 Jun 2026 18:38:33 -0400 Subject: [PATCH] release scripts: push the release branch to both forges Push to the 'all' remote (GitHub + Gitea pushurls) instead of origin so releases are mirrored to Gitea too. CI still triggers via the GitHub pushurl. Co-Authored-By: Claude Opus 4.8 (1M context) --- create_release.sh | 4 +++- scripts/release.sh | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/create_release.sh b/create_release.sh index 10cff6b..b254165 100755 --- a/create_release.sh +++ b/create_release.sh @@ -26,7 +26,9 @@ echo "Merging $MAIN_BRANCH into $RELEASE_BRANCH..." git merge $MAIN_BRANCH --no-ff -m "Release $VERSION" echo "Pushing $RELEASE_BRANCH..." -git push origin $RELEASE_BRANCH +# Push to the 'all' remote so the release branch lands on both GitHub and Gitea. +# CI (GitHub Actions) still triggers via the GitHub pushurl. +git push all $RELEASE_BRANCH git checkout $MAIN_BRANCH diff --git a/scripts/release.sh b/scripts/release.sh index 096c45c..bcbf9ee 100755 --- a/scripts/release.sh +++ b/scripts/release.sh @@ -34,4 +34,6 @@ vim "$CHANGELOG" # Commit and push git add "$CARGO_TOML" "$CHANGELOG" git commit -m "Release v${new_version}" -git push --force origin "$(git branch --show-current):release" +# Push to the 'all' remote so the release branch lands on both GitHub and Gitea. +# CI (GitHub Actions) still triggers via the GitHub pushurl. +git push --force all "$(git branch --show-current):release"