How it works
1
2
Create on demand or automate
Click New post on the Content page to generate a changelog right now, or set up a schedule or an event trigger so Notra generates one for you. See Scheduled Automation and Event-Based Automation.
3
Notra reads your activity
The changelog agent pulls the activity inside the lookback window, filters out work that is only relevant internally, and groups the rest by impact and category.
4
Review and publish
The changelog appears as a draft in a collection. Open it, edit it directly or ask the content agent for changes, then click Publish.
Create a changelog manually
1
Open the create dialog
Go to Content and click New post.
2
Formats
Pick Changelog entry. You can select several formats at once, for example a changelog plus a LinkedIn post, and Notra generates all of them from the same activity. Choose a lookback window and toggle which data points to include: Pull Requests, Commits and Releases.
3
Activity
Pick the repositories and Linear integrations to draw from, and Notra previews the releases, pull requests, commits and issues in the window. Deselect anything you do not want mentioned, and search by title, author or label to find items.
4
Identity
Choose which brand identity writes the post. Notra then generates the posts into a new collection and opens each one in the editor when it is ready.
Changelog structure
Every generated changelog follows the same shape.Summary
The summary is a single paragraph directly under the title, and the agent targets 120 to 180 words and goes shorter when there is less to cover.Highlights
Highlights lists up to five changes, chosen by importance in this order: security, breaking changes, major features, reliability fixes, performance. If there are fewer than five high-impact changes, the list is shorter, because the agent never pads it.The agent excludes low-signal work such as small refactors, dependency bumps, wording tweaks and test-only changes from Highlights. It leaves that work out of the changelog entirely unless it has a clear effect on your audience.
More updates
Every remaining change appears exactly once as a bullet under one of these categories:- Security
- Features & Enhancements
- Bug Fixes
- Performance Improvements
- Infrastructure
- Internal Changes
- Testing
- Documentation
Lookback windows
The lookback window controls how far back Notra looks for activity when it generates a changelog on demand or on a schedule.Event triggers do not use a lookback window, so for a GitHub release event, Notra compares the new release with the previous one and uses that range.
Tone
The agent writes in the tone profile of the brand identity you pick: Conversational, Professional, Casual or Formal. You set it under Studio > Brand Identity, together with your target audience and custom instructions. See Brand Voice.Automation settings
Auto-publish
Changelogs and blog posts support Auto-publish, and when it is on, Notra saves generated posts with thepublished status immediately instead of as drafts. Notra always saves social posts and images as drafts.
Publishing
Clicking Publish in the editor (or enabling auto-publish) sets the post status topublished but does not push the post anywhere by itself. Instead, your publishing destinations pick up published posts:
- Framer: the Notra plugin imports your posts into a Framer site. See Framer.
- Manual: copy the Markdown from the editor.
draft.
Edit with the content agent
Every post has a content agent in the right-hand panel. Select text in the editor to give the agent context, then ask for changes such as:- “Expand the summary to mention the pricing change”
- “Simplify the Highlights for a non-technical audience”
- “Move the caching change into Performance Improvements”
Best practices
Write clear PR titles and descriptions
Notra uses your PR titles and descriptions as source material, so descriptive PRs produce better changelogs. Good PR titleAdd email verification flow with expiration handling
Poor PR titleFix bug
Match the lookback window to your release cadence
- If you ship daily, use
yesterdayorcurrent_day - For weekly releases, use
last_7_days - For monthly updates, use
last_30_days
Review before publishing
Changelogs stay drafts until you publish them, so use the review to:- Verify technical accuracy
- Add context that GitHub activity does not capture
- Adjust the Highlights for your audience
Example changelog
Common issues
Changelog is too short or missing expected changes
The lookback window may not cover the relevant timeframe, the activity may have been deselected in the Activity step or the PRs may lack detail. To fix it:- Check the lookback window against when the work was merged
- Make sure the PRs, commits or releases were selected in the Activity step
- Add descriptive titles and descriptions to your PRs
Nothing was generated
Every plan includes a monthly quota of long-form posts, and changelogs and blog posts count against it. When the quota is used up, Notra falls back to AI credits, and if none are available, Notra blocks the generation. To fix it, check Settings > Billing & Usage > Usage, and top up credits under Settings > Credits or upgrade the plan. See Billing & Plans.Changes from private repositories not appearing
The GitHub app is not installed on the repository, or the repository is disabled in the integration. To fix it:- Navigate to Integrations > GitHub
- Add the repository, or enable it if it is already listed
- Re-run the generation