Anyone can list commits — the value is that they come back sorted into features, fixes and the rest with authorship stats attached, ready to paste into a release. It uses GitHub's `since` parameter to cut API calls where it can and falls back to SHA filtering otherwise, which matters on repositories with long histories.
A single-tool server that reads a repository's commits over a range you specify, groups them by conventional-commit type, enriches them with pull request data where available, and returns formatted markdown.
- Release notes generated for an owner and repo over a commit range you give as `fromCommit` and `toCommit` — `generate_release_notes`
- Commits grouped into sections: features, fixes, documentation, performance, refactoring, tests, build and other
- Optional statistics — total commits, breaking changes, and breakdowns by type and by author — controlled with `includeStats`
- Commits enriched with their pull request data when one exists, and newest-first ordering throughout
A GitHub personal access token with repo access, in `GITHUB_TOKEN`. Node dependencies installed and built; the client runs `build/index.js`. The package is `release-notes-server` 0.1.0.
One command plus a key — npx -y github:nickbaumann98/release-notes-server, then supply credentials