-
Notifications
You must be signed in to change notification settings - Fork 0
chore: PR title lint + release-drafter #12
Copy link
Copy link
Closed
Labels
choreMaintenance, tooling, infraMaintenance, tooling, infraciCI workflows and gatesCI workflows and gatesharnessCross-cutting harness mechanics (controls, hooks, gates)Cross-cutting harness mechanics (controls, hooks, gates)releaseRelease automation, SBOM, tagsRelease automation, SBOM, tags
Metadata
Metadata
Assignees
Labels
choreMaintenance, tooling, infraMaintenance, tooling, infraciCI workflows and gatesCI workflows and gatesharnessCross-cutting harness mechanics (controls, hooks, gates)Cross-cutting harness mechanics (controls, hooks, gates)releaseRelease automation, SBOM, tagsRelease automation, SBOM, tags
Problem
Conventional commit titles drive release-drafter categorisation. If title-lint and the drafter share no source of truth for allowed prefixes, drafted release notes are wrong.
Proposed solution
Port
.github/workflows/pr-title.ymlenforcing the 7-prefix schema (feat/fix/docs/test/refactor/chore/release). Port.github/release-drafter.ymlwith categories mirroring the schema and a version-resolver. Wire.github/workflows/release-drafter.ymlto update the draft release onmainpush and PR label/open/reopen/synchronize events.Acceptance criteria
wip: ...fails the lint job.feat: ...PR adds a line under "Features" in the draft release.fix: ...PR adds a line under "Bug Fixes".Priority rationale
High: release notes are part of the portfolio surface; they need to be drafted automatically and correctly.
Depends on
#2