GitHub Release Notes and Changelog From Merged Pull Requests
Turn a list of pull requests into user-facing release notes.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Write release notes from these merged pull requests (titles, labels and short descriptions): [PULL_REQUEST_LIST]. Version and date: [VERSION_AND_DATE]. Audience: [AUDIENCE]. Breaking changes I know of: [BREAKING_CHANGES]. Credit contributors by username: [CREDIT_CONTRIBUTORS]. Group changes into Added, Changed, Fixed, Deprecated, Removed and Security following a changelog convention, as Markdown I can save as CHANGELOG.md. Write each item from the user's point of view in one or two sentences without internal jargon. Put breaking changes first with migration steps. Credit contributors only if I said so. Leave out purely internal changes and list them separately for confirmation. Mark items with thin descriptions [NEEDS DETAIL], and do not claim performance gains or security fixes unless the pull request text says so. Add a short announcement paragraph, a one-line summary for a social post, and a version for a non-technical stakeholder. Keep it accurate, neutral and readable. Keep the order of items the same in every release so readers know where to look. If two pull requests describe one change, merge them into one line and tell me.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.