Gitea Actions: workflow guards + .gitea release pipeline#7
Merged
Conversation
…patch Gitea reads .github/workflows/ for compatibility, so without guards it tries to run the release and wiki-sync workflows on Gitea too - which fail because they use softprops/action-gh-release@v2 (GitHub-only) and push to GitHub-hosted wiki URLs. Add `if: github.server_url == 'https://github.com'` to the release-builder and wiki-sync jobs so Gitea no-ops them. ci.yml (plain dotnet build + test) still runs on both, and now also accepts workflow_dispatch so it can be triggered by hand to verify a self- hosted runner is picking up jobs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
.gitea/workflows/release.yml runs on the self-hosted Windows runner when a v* tag is pushed (or via workflow_dispatch with a version override for testing without bumping the project). Mirrors the GitHub release workflow shape - dotnet test, choco-install Inno Setup if missing, run scripts/build-installer.ps1 - then uses Gitea's REST API directly for the release-creation + asset-upload steps (Gitea has no equivalent to softprops/action-gh-release). Token is the runner-injected secrets.GITHUB_TOKEN, which Gitea provides for GitHub Actions compatibility. Path location matters: lives under .gitea/ so GitHub Actions never sees it, while the existing .github/workflows/release.yml stays GitHub-only (already gated with `if: github.server_url == ...`). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Gitea-side CI/release support
.github/workflows/{release,wiki-sync}.ymlgetif: github.server_url == 'https://github.com'guards so they no-op when Gitea picks them up.ci.ymlstill runs on both (plain dotnet build + test) and now also acceptsworkflow_dispatchfor manual testing..gitea/workflows/release.ymlis the Gitea twin of the release pipeline: builds the installer on the self-hosted Windows runner, uses Gitea's REST API to create the release and attach the installer (sincesoftprops/action-gh-releaseis GitHub-only).After merge:
workflow_dispatchthe CI workflow from the Gitea Actions UI to verify the runner is wired up; pushingv0.1.4(or any future tag) will then build installers on both platforms in parallel.Generated with Claude Code