argoyle
d5623bdf9c
The PR creation curl immediately follows branch creation via the Contents API, but Gitea may not have fully indexed the new branch for pull request operations yet. This causes intermittent HTTP errors on the first run. - Add sleep 3 before PR creation to allow Gitea to process the new branch - Use --retry-all-errors so curl retries on HTTP 4xx/5xx (not just connection failures) - Capture and display the actual HTTP error code and response body on failure for easier debugging Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Shared Workflows
Reusable Gitea Actions workflows for Unbound Software repositories.
Available Workflows
Release.yml
Automated release workflow using git-cliff for changelog generation.
Usage:
name: Release
on:
push:
branches: [main]
jobs:
release:
uses: unboundsoftware/shared-workflows/.gitea/workflows/Release.yml@main
Inputs:
tag_only(boolean, default:false): Set totrueto only create tags without full releases
Requirements:
This workflow reads the release token from /runner-secrets/release-token, which is automatically available on Unbound's Gitea runners. No repository secrets need to be configured.
How it works:
- On each push to the default branch, generates a changelog using git-cliff
- Creates or updates a
next-releasebranch with the updated CHANGELOG.md and .version file - Opens or updates a PR titled "chore(release): prepare for vX.Y.Z"
- When the .version file exists (after merging the release PR), creates a Gitea release with the changelog