Relgen — Generate release notes from GitHub activity in under 5 minutes

[sstankala]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Apps

Body

Hey GitHub community,

I built a PoC called Relgen that automates release note generation from a repo's merged PRs, commits, and linked issues.

What it does:

Fetches merged PRs, commits, issues, and milestones via GitHub REST API
Categorizes changes (features, fixes, security, performance) using label matching
Generates editable, source-linked release notes — static or AI-assisted
PAT and LLM API keys stay client-side only — nothing stored server-side

GitHub APIs used:
GET /repos/{owner}/{repo}/pulls — merged PRs with labels and linked issues
GET /repos/{owner}/{repo}/commits — commit range filtering
GET /repos/{owner}/{repo}/milestones — scoped release grouping
LLM options: No LLM (static), HuggingFace shared inference, or BYOK (Claude / GPT-4o / Gemini)

Access:Free for open source projects — just point it at your public repo. ( Connect with me, I can give the beta access)

Try it: https://sstankala-releasegen-ai.hf.space/ — no account needed.

Would love feedback from anyone who works on release workflows or uses the GitHub API heavily. Particularly curious if there are API patterns I'm not leveraging well.

Disclosure: Developed this through vibe coding (Claude code plugin)
Check quick summary of the tool:
Relgen-v2.pdf

Goal: release to GitHub market place

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐