All examples
GitHub

Publish a release with generated notes on GitHub

One 2:57 screen recording, 9 clicks, no script. TurtleScene turned it into everything below. Nothing was edited by hand.

In2:57 recording
Out19
  • 10 videos
  • 1 clickable demo
  • 2 GIFs
  • 2 thumbnails
  • 2 caption tracks
  • 1 help article
  • 1 set of launch posts
The three main outputs

Watch it, click through it, or share the story.

Script, AI voiceover, zooms and a highlight on each step, all generated from the recording. Turn the sound on.

Cut for social · 8 videos

Every shape a feed asks for.

Captions are burned in, in big phrases, so they play muted. The narrated video gets vertical and square cuts that follow every click under a step header, and a 30-second highlight in landscape and 9:16. The story video is laid out again for each shape: vertical and square cuts, and its highlight in landscape and 9:16.

Vertical cut
Reels, Shorts, TikTok · 1:25
Square cut
LinkedIn and X · 1:25
30-second highlight
Emails and landing pages · 0:32
Vertical highlight
Stories and ads · 0:32
Written from the same recording

The docs and the launch copy come with it.

Help article

How to publish a release with generated notes on GitHub

Use this walkthrough to create a new GitHub release, generate release notes automatically, and publish the release. Follow the steps in order if you are doing this for the first time.

1. Open the releases page

Open the releases page

From the repository homepage, click the latest release tag, shown as v2.3.0 Latest. This opens the releases page, where you can see the current release details.

2. Start a new release

Start a new release

Click Draft a new release. The release creation form opens, with the tag and title fields filled in.

3. Open the tag menu

Open the tag menu

Click Select tag. This opens the tag dropdown so you can choose an existing tag or create a new one.

4. Create a new tag

Create a new tag

In the tag menu, look for v2.4.0. If no matching tag appears, click Create new tag to start defining it.

5. Confirm the tag

Confirm the tag

Click Create to finalize the new v2.4.0 tag. You return to the release form with Tag: v2.4.0 selected.

6. Generate release notes

Generate release notes

Click Generate release notes. GitHub automatically fills the release notes editor with notes based on merged pull requests.

7. Enter the release title

Enter the release title

Click in Release title and type the title you want for this release. This updates the release title on the form.

8. Add your own release details

Add your own release details

Click in Release notes and add your own summary text at the top. Your custom text appears above the generated sections.

9. Publish the release

Publish the release

Review the form, then click Publish release when everything looks ready. GitHub opens the published release page, where you can see contributors and assets.

Your release is now live, with generated notes and your own summary included.

Launch posts
You
Your company
LinkedIn post · written by TurtleScene

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

You
Your company
X post · written by TurtleScene

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

Read the blog post

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.

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.

Captions · narrated video
  1. 00:00Here's how to publish a release
  2. 00:01with generated notes on GitHub.
  3. 00:04From the repository homepage,
  4. 00:07open the releases page
  5. 00:09by selecting v2.3.0 Latest.
  6. 00:12The releases page opens
  7. 00:13with the current release details visible.
  8. 00:17Start a new release
  9. 00:18by choosing Draft a new release.
  10. 00:21The new release form opens,
  11. 00:23and the tag and title are filled in.
  12. 00:27Open the tag menu by clicking Select tag.
  13. 00:32With no matching tag shown for v2.4.0,
  14. 00:35use Create new tag to define it.
  15. 00:40Confirm the new v2.4.0 tag
  16. 00:43by pressing Create.
  17. 00:46GitHub returns to the form
  18. 00:49with Tag: v2.4.0 selected.
  19. 00:52Use Generate release notes
  20. 00:53to fill the notes automatically.
  21. 00:56GitHub adds generated notes
  22. 00:58in the release notes editor.
  23. 01:01Place the cursor in Release title
  24. 01:03to enter a title.
  25. 01:05The title is updated,
  26. 01:06and custom text is added above the notes.
  27. 01:10Click into Release notes
  28. 01:11to add your own summary text.
  29. 01:14The release notes show the added
  30. 01:16summary above the generated sections.
  31. 01:19When everything looks ready,
  32. 01:21publish it with Publish release.
  33. 01:24GitHub opens the published release page
  34. 01:26with contributors and assets shown.
  35. 01:30The new release
  36. 01:31is now published on GitHub.
Captions · story video
  1. 00:00Here's how to publish a release
  2. 00:01on GitHub, with notes generated
  3. 00:03from your merged pull requests.
  4. 00:06Writing release notes by hand means
  5. 00:08digging through every merged change.
  6. 00:11From the Releases page, choose Draft
  7. 00:14a new release. Type a version,
  8. 00:16pick Create new tag, then confirm it
  9. 00:19to create the tag on publish.
  10. 00:22Next, click Generate release notes
  11. 00:24to list what changed since the last tag.
  12. 00:28Add a title, then choose Publish release.
  13. 00:32The release goes live, marked Latest,
  14. 00:35with notes grouped into new features,
  15. 00:37improvements and bug fixes,
  16. 00:39each linked to its pull request.
  17. 00:42Next time you ship, let GitHub draft
  18. 00:45the notes, then review and publish.
For previews and link cards

GIFs and thumbnails, from both videos.

GIF · narrated video
GIF · narrated videoChangelogs, READMEs, emails
GIF · story video
GIF · story videoChangelogs, READMEs, emails
Thumbnail · narrated video
Thumbnail · narrated videoYouTube and link previews
Thumbnail · story video
Thumbnail · story videoYouTube and link previews

Independent tutorials we recorded ourselves. GitHub is a trademark of their owners; TurtleScene is not affiliated with or endorsed by them.

Your next product demo is one recording away

Record a flow on the free plan and watch it come back narrated, clickable and on-brand in a few minutes.

  • No credit card
  • 2 free recordings a month
  • Cancel any time