Skip to content

chore(github): add release notes template with contributor attribution - #90

Merged
mhaadiabu merged 1 commit into
Owusu1946:devfrom
mhaadiabu:chore/release-template-dev
Oct 8, 2026
Merged

mhaadiabu merged 1 commit into
Owusu1946:devfrom
mhaadiabu:chore/release-template-dev

Conversation

@mhaadiabu

@mhaadiabu mhaadiabu commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

Expojet releases (e.g. v0.8.0) are hand-written: a bespoke What's new list with no per-contributor attribution and no contributors summary. GitHub can generate that automatically, where every entry attributes its author (title by @author in #number), followed by New Contributors, a Full Changelog compare link, and an automatic Contributors avatar grid.

Solution

Add .github/release.yml so any Expojet release created with Generate release notes renders in that shape:

  • single What's Changed catch-all, so unlabeled PRs are never silently dropped
  • excludes bot authors (dependabot, github-actions) and closed-as-noise labels (duplicate, invalid, wontfix, question)
  • documents the skip-changelog label opt-out in the file header

No workflow changes: the publish pipeline doesn't create GitHub Releases itself, so this takes effect whenever notes are generated for a release (releases page, gh release create --generate-notes, or the API flag).

Combinations checked

  • New file only; no generator, adapter, CLI, or workflow behavior changes.
  • YAML shape sanity-checked; single catch-all category verified against GitHub release.yml semantics.

@vercel

vercel Bot commented Oct 8, 2026

Copy link
Copy Markdown

@mhaadiabu is attempting to deploy a commit to the okenneth2266-1523's projects Team on Vercel.

A member of the Team first needs to authorize it.

@mhaadiabu mhaadiabu changed the title chore(github): add release notes template mirroring t3code format chore(github): add release notes template with contributor attribution Oct 8, 2026
@mhaadiabu
mhaadiabu merged commit 08f2c79 into Owusu1946:dev Oct 8, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant