Makis Papas

ReleaseJet - Github Actions / Gitlab CI release notes from closed issues

by
Per-customer release notes, generated from the issues your team already labels — no Conventional Commits, no changeset files, no PM chasing developers. Everything is configured via a single .releasejet.yml — label→category mapping, multi-client prefixes, GitHub/GitLab providers

Add a comment

Replies

Best
Makis Papas
Maker
📌

Hello,

My team and I have worked on multi-client repos for years and never adopted Conventional Commits. But our issues were always well labeled.

I built ReleaseJet so we (and our PM) could get automated release notes without changing how we commit.

The flow

  1. Set up the GitHub Action / GitLab CI once

  2. Close sprint issues as usual

  3. Tag a release (e.g. v1.0.0, or client1-v1.0.0 for multi-client monorepos)

  4. CI publishes a Release with issues grouped by category

You can check the demo-repo for more info.

I'm curious about how you solved this issue. Feel free to propose changes or a feature that the app is missing.