k3nny/releaser
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 14 Wiki Activity

ci(github): add GitHub Actions CI and release workflows for k3nnyfr/releaser mirror
ci / vet, staticcheck, test, build (push) Canceled after 0s
Details
docs / Build and deploy docs (push) Canceled after 0s
Details

Browse Source 
- .github/workflows/ci.yml: same vet/staticcheck/test/build checks as Gitea CI
- .github/workflows/release.yml: same five binaries and build flags as the
  Gitea release workflow, published with gh release create
- docs: mention the GitHub mirror and both release pages; GitHub Actions
  example downloads from GitHub releases using RUNNER_OS/RUNNER_ARCH
- docs: fix broken latest/download URL, clone URL and Go version requirement

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
k3nny
2026-09-24 22:38:17 +02:00
co-authored by Claude Opus 5.5
parent 37db8e97ca
commit e28434a030
7 changed files with 166 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/content/_index.md
+1 -1
View File
@@ -4,7 +4,7 @@ title: releaser
**CI-friendly release automation for GitFlow workflows using Conventional Commits.**
[Source code](https://git.k3nny.fr/k3nny/releaser) · [Releases](https://git.k3nny.fr/k3nny/releaser/releases)
[Source code](https://git.k3nny.fr/k3nny/releaser) · [Releases](https://git.k3nny.fr/k3nny/releaser/releases) · [GitHub mirror](https://github.com/k3nnyfr/releaser)
Standard tools like `semantic-release` are designed for trunk-based development. In a GitFlow setup with versioned release branches (`release/1.1`, `release/1.2`), they either fail to respect the branch's version range or require brittle configuration.