if-changed 0.3.4

A pre-submit for file changes.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

name: Release Notes

on:
  workflow_dispatch:
    inputs:
      tag:
        description: "Release tag (e.g. v0.3.0)"
        required: true
        type: string

concurrency:
  group: release-notes-${{ github.event.inputs.tag }}
  cancel-in-progress: true

jobs:
  enhance:
    name: Enhance release notes with Claude
    runs-on: ubuntu-latest
    permissions:
      contents: write
      id-token: write
    steps:
      - name: Checkout
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          fetch-depth: 0

      - name: Write release notes with Claude
        uses: anthropics/claude-code-action@26ec041249acb0a944c0a47b6c0c13f05dbc5b44 # v1
        with:
          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
          claude_args: --allowedTools "Bash(git log:*),Bash(git describe:*),Read,Write"
          prompt: |
            Write an exciting, polished GitHub release body for if-changed ${{ inputs.tag }} and save it to `release-notes.md`.

            if-changed is a Rust CLI tool for incremental builds — it conditionally runs commands only when specified files have changed. It's designed for use in build scripts, CI pipelines, and Makefiles to skip redundant work.

            Steps:
            1. Run `git describe --tags --abbrev=0 HEAD^` to get the previous tag, then run `git log <previous-tag>..HEAD --oneline` to see all commits in this release.
            2. Read `README.md` and `src/` files to understand the CLI API and use cases.
            3. Write the release body to `release-notes.md`. It should:
               - Open with an enthusiastic one-paragraph summary of what's new or why this release is exciting.
               - Have clearly labelled sections (e.g. **✨ New Features**, **🐛 Bug Fixes**, **⚡ Improvements**) — only include sections that actually have content.
               - For any significant new feature, include a short shell example showing it in action.
               - End with an installation snippet (`cargo install if-changed`).
               - Be written in an upbeat, developer-friendly tone — celebrate the work!
            Do NOT publish it yourself — a subsequent step will do that.

      - name: Publish release notes
        uses: softprops/action-gh-release@a06a81a03ee405af7f2048a818ed3f03bbf83c7b # v2
        with:
          tag_name: ${{ inputs.tag }}
          body_path: release-notes.md