You know that feeling.
It’s Friday afternoon.
The sun is shining (or the rain is pouring, depending on where you live), and your team has just wrapped up a sprint.
You’ve deployed code, fixed bugs, and maybe even sneaked in a feature or two.
You’re ready to close your laptop and grab a cold beverage.
But wait.
A Slack notification pops up.
“Hey, can you send out the release notes?”
The dread sets in.
You open GitHub.
You scroll through the closed Pull Requests. “Fix typo,” “Update dependency,” “WIP,” “Revert ‘WIP’,” “Actually fix the thing,” “Merge branch ‘main’ into ‘feature/fix-typo’.” It’s a mess. Organizing this into something your manager (or your users) can actually read is a task that sucks the soul right out of your weekend.
Meet the “Release Notes Generator”
I built a tool—let’s call it Release-Relay.
It’s a CLI tool that does the heavy lifting for you.
It connects to your GitHub repository, grabs all the merged PRs between two dates, and turns them into a beautiful, structured Markdown report.
But it’s not just a git log dump.
Oh no, we have standards here.



During the holidays, I had a bit of time to do some fun stuff with Actions on Google.






