T

This is placeholder commit and will be replaced by a merge of your virtual branches.

Due to GitButler managing multiple virtual branches, you cannot switch back and
forth between git branches and virtual branches easily. 

If you switch to another branch, GitButler will need to be reinitialized.
If you commit on this branch, GitButler will throw it away.

For more information about what we're doing here, check out our docs:
https://docs.gitbutler.com/features/branch-management/integration-branch

2026-01-08 20:58:11 +01:00

.gitea/workflows

feat: add Release workflow for automated releases

2026-01-08 19:06:52 +01:00

README.md

feat: add Release workflow for automated releases

2026-01-08 19:06:52 +01:00

renovate.json

Add renovate.json

2026-01-08 19:17:04 +00:00

README.md

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
    secrets:
      UNBOUND_RELEASE_TOKEN: ${{ secrets.GIT_API_TOKEN }}

Inputs:

tag_only (boolean, default: false): Set to true to only create tags without full releases

Secrets:

UNBOUND_RELEASE_TOKEN (required): Token with API access to create PRs and releases. Required scopes: repository (read/write), issue (read/write)

How it works:

On each push to the default branch, generates a changelog using git-cliff
Creates or updates a next-release branch 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 GitHub release with the changelog