patch-notes

To generate player-facing patch notes from git history, aggregate your development logs and sprint data, then translate technical changes into categorized release notes. This process converts internal commit messages into a coherent narrative for your players.

Organizing game patch notes by category involves sorting development updates into new content, balance changes, fixes, and known issues. This categorization translates technical updates into structured, player-friendly release communications.

You can automate release notes generation by parsing sprint data and internal changelogs to output a cohesive patch narrative. This automated translation saves time by converting technical balance documentation into player-facing wording.

Converting technical changelogs into player-friendly wording requires parsing internal development updates and categorizing them into new content and fixes. This translates technical language into a clear narrative output for publication.

You need to provide a specific version number to generate the corresponding patch notes. The system parses this version input to output the final release notes file at production/releases/[version]/patch-notes.md.

Automated patch notes are outputted as a Markdown file at production/releases/[version]/patch-notes.md. This format organizes categorized changes into a coherent narrative ready for easy publishing.