Check merge history
ReleaseMind uses merge history to map PRs to tags.
If PRs were squash-merged, confirm the commits are included in the tag.
Confirm tag coverage
Compare the tag commit to the previous release tag to verify the range.
If the tag is on the wrong branch, move it to the correct release commit.
Regenerate the draft
Once the tag and PRs are aligned, regenerate the draft.
If it still looks incomplete, contact support.
Review and introspect
PR mapping improves with consistent workflow hygiene.
- Do you need a consistent merge strategy to improve PR mapping?
- Are PR titles and descriptions detailed enough for summaries?
- Should you add a release checklist to avoid missing PRs?