Connect the workflow you already use
Install the GitHub App, select a repository and branch, and continue shipping with semantic version tags. There is no separate release document to maintain.
GitHub release notes generator
Turn GitHub releases into communication your whole company can use.
Connect a repository and release branch. When your team ships a version, ReleaseView prepares a clear draft from the work behind it and keeps the final decision with you.
Trace every draft to source
Review the commits behind a release note and follow links back to GitHub when a detail needs verification before approval.
Publish beyond GitHub
Create a public changelog and distribute one plain-language Audience email manually or with optional automation. Published releases are also available through REST and MCP interfaces.
Example workflow
A version tag becomes a useful release update
Your team tags v2.4.0 after shipping several pull requests. Instead of searching chat and GitHub to reconstruct the release, you begin with the commits behind that version.
- 01
Ship a version
A semantic version tag on the selected repository starts a draft for the relevant changes.
- 02
Check the source
Follow links to the commits behind each item and correct anything the draft missed.
- 03
Approve and share
Publish the release to your changelog and send the appropriate update to subscribers.
Common questions
How does ReleaseView know when a release ships?
ReleaseView tracks the repository and branch you select. A new semantic version tag can trigger a draft for the relevant range of commits.
Does ReleaseView change my repository?
ReleaseView reads the authorized repository data needed to prepare release notes. It does not modify your code or repository settings.
Can I create a release note manually?
Yes. You can create a release for a chosen version and select the commits that should inform the draft.