Skip to content

ci(changelog-review): extract as reusable workflow once shape is proven #1304

@claude

Description

@claude

Context

From PR #1302 follow-up (not blocking):

Consider extracting the workflow into laurigates/.github as reusable-changelog-review.yml once the new shape is proven — per .claude/rules/ci-cd-workflows.md we prefer reusable workflows for cross-repo automation, though this one is plugin-collection specific so reuse value is currently low.

When to act

After the triage-only shape is validated across 2–3 stable weekly runs.

Design notes

  • Target: laurigates/.github repo as reusable-changelog-review.yml
  • Inputs would need to be parameterized: the tracking JSON path, label names, candidate rules file mapping
  • The keyword→candidate-rules mapping is currently hardcoded to this repo's rule paths — that section would need to be either generic or accept a mapping input
  • Reuse value is currently low (plugin-collection specific), so the trigger should be actual demand from a second repo needing the same automation

Acceptance criteria (if pursued)

  • Reusable workflow lives in laurigates/.github
  • Caller in this repo is a thin wrapper (uses: laurigates/.github/.github/workflows/reusable-changelog-review.yml@main)
  • Keyword→candidate-rules mapping is parameterized or made repo-agnostic
  • Existing weekly schedule and workflow_dispatch inputs are preserved

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions