Configure Tagline

[tagline-agent]

Thanks for installing Tagline! 👋

This PR adds a default .release-agent.md so Tagline has somewhere to look for your branch + release-notes-tone preferences. Edit it freely before merging — every section is optional.

One more thing — add the release workflow

Tagline writes nothing to your repo directly. The release work runs inside your own CI via a GitHub Action. Add this file to your repo at .github/workflows/release-agent.yml:

name: Release Agent
on:
  # Phase A — propose: opens a release PR with version bump + CHANGELOG.
  # No tag or GitHub Release is created here.
  workflow_dispatch:
    inputs:
      release_plan:
        required: true
        type: string
      issue_number:
        required: false
        type: string
        default: ""
      dry_run:
        required: false
        type: boolean
        default: false
  # Phase B — finalize: tags the merge commit + publishes the GitHub
  # Release once the release PR is merged into the production branch.
  # Triggered on `push` because PRs opened with GITHUB_TOKEN do NOT fire
  # `pull_request: closed` events (GitHub anti-recursion behavior). The
  # action self-filters and no-ops for non-release pushes.
  push:
    branches: [main, master]
jobs:
  release:
    if: ${{ github.event_name == 'workflow_dispatch' || github.event_name == 'push' }}
    runs-on: ubuntu-latest
    permissions:
      contents: write
      pull-requests: write
      issues: write
    steps:
      - uses: actions/checkout@v4
        with: { fetch-depth: 0 }
      - uses: HelicanHQ/tagline-release-agent-action@v1
        with:
          release_plan: ${{ inputs.release_plan }}
          github_token: ${{ secrets.GITHUB_TOKEN }}
          issue_number: ${{ inputs.issue_number }}
          dry_run: ${{ inputs.dry_run }}

How the release flow works

Once the workflow is in place, Tagline watches PRs merged into your production branch. When the first PR after a release lands, it opens a release-tracking issue labeled tagline:release-pending and keeps it up to date as more PRs merge.

That issue is the only place slash commands work:

• /release-report — preview the release (changelog + plain-language summary + suggested bump)
• /approve — ship it

Comments on any other issue or PR are silently ignored, so the bot stays quiet on unrelated conversations.

Checklist

• Review (or edit) .release-agent.md.
• Add .github/workflows/release-agent.yml with the YAML above.
• Add an AI_API_KEY repository secret (any OpenAI-compatible provider).
• Merge this PR.

Questions? See the docs.