app-store-changelog

You can generate App Store release notes by parsing git commit history to filter user-impacting changes. The tool analyzes commit ranges since the last git tag, categorizing feature updates, bug fixes, and performance improvements into a polished "What's New" list.

Filtering internal refactoring commits from release notes requires intelligent categorization of git logs. This tool distinguishes user-facing features from internal technical work like CI updates, ensuring only benefit-focused updates appear in the final App Store documentation.

Yes, you can use git tags to define commit ranges for generating documentation. The tool automatically gathers commits and touched files since the last version tag to ensure the release notes accurately reflect the scope of the new update.

Yes, git access is required to categorize feature updates and bug fixes for the App Store. The tool needs repository access to parse commit ranges and evaluate changes based on predefined release note guidelines.

Generated changelogs may contain technical jargon if the intelligent filtering fails to classify internal work correctly. The tool is designed to prevent this by distinguishing user-facing features from technical refactors or CI updates before generating the notes.