# Launch posts

## LinkedIn

Release notes are useful right up until you have to write them by hand.

This walkthrough shows how to publish a release on GitHub with notes generated from merged pull requests, so first-time users can see exactly where to click and what happens next.

In the video, you’ll see how to:

• open the Releases page and choose **Draft a new release**
• enter a version and select **Create new tag**
• confirm the tag so it’s created when you publish
• click **Generate release notes** to pull in changes since the last tag
• add a title and choose **Publish release**

Once published, the release appears as **Latest**, with notes grouped into new features, improvements, and bug fixes. Each item links back to its pull request, making the release easier to review and easier to share.

If you’ve never used generated release notes in GitHub before, this is a simple place to start. Watch the video to see the full flow. #GitHub #ReleaseManagement #DevTools

## X

Stop writing release notes by hand. This video shows how to publish a GitHub release with generated notes from merged pull requests—tag it, generate the notes, review, and publish. Watch the walkthrough. #GitHub #DevTools

## Blog: How to publish a release with generated notes on GitHub

## A faster way to draft release notes

Writing release notes manually usually means retracing every merged change and turning pull requests into something readable. This video walkthrough shows a simpler path in GitHub: generate release notes automatically, review them, and publish the release.

It’s a practical how-to for first-time users who want to understand both the feature and the steps involved.

[VIDEO]

## What the video covers

The walkthrough starts on the GitHub Releases page, where you choose **Draft a new release**. From there, the flow is straightforward:

- enter a version number
- choose **Create new tag**
- confirm that the tag should be created when the release is published
- click **Generate release notes**
- add a release title
- select **Publish release**

GitHub then drafts notes based on what changed since the previous tag, using merged pull requests as the source.

## What you get after publishing

Once the release is live, it appears as **Latest** and includes generated notes organized into clear sections:

- new features
- improvements
- bug fixes

Each entry links back to its pull request, which makes it easier to trace changes and review what shipped.

## Why this workflow is useful

The value here is clarity and speed. Instead of manually collecting merged work and formatting it into release notes, you can let GitHub assemble a first draft from recent changes. That gives you something structured to review before publishing.

For teams or maintainers shipping regularly, this can make the release process more repeatable. For anyone new to GitHub releases, it also removes some of the guesswork around tagging, drafting, and publishing.

## Watch the step-by-step walkthrough

If you want to see exactly where to click and how the generated notes appear, watch the video and follow the full release flow from draft to publish.