Before you run
Create or confirm the release tag in GitHub; semantic tags are easiest to read.
Merge PRs into the default branch so ReleaseMind can see the full context.
Ensure the tag points at the intended release commit.
Trigger a draft
In Release Studio, choose the repo and select Generate draft.
Wait for processing to complete; large repos may take a few minutes.
Open the draft to view the summary and grouped changes.
- Use a tag that matches your release workflow (for example v1.2.0)
- Watch the status indicator for queued or processing states
- Refresh once if the status stalls
Review the output
Scan the summary for the main outcomes and any breaking changes.
Check that the PR list matches what merged since the previous tag.
Edit the draft before publishing if you need to clarify language or reorder sections.
If the draft is empty or incomplete
Make sure PRs are merged and included in the tag boundary.
GitHub indexing can lag; wait a few minutes and refresh.
If the draft is still missing items, contact support with the repo name and tag.
Review and introspect
Your first draft is the baseline for every release that follows.
- Did the draft match the story you want to share with users?
- Are there labels or PR titles you should tighten for future drafts?
- Do you need to adjust your tagging cadence or release rhythm?