Generate release notes from a branch comparison

Use release notes generation to turn a reviewed comparison between two branches into a draft changelog.

Choose the comparison

Open Release Notes in the repository tools. Select the connected provider repository, the base branch representing the starting point and the compare branch containing the changes to describe.

Branch direction matters. Compare the newer work against the intended baseline; reversing the two can describe a different set of changes.

Review the diff

Continue to the diff review and inspect the changed files and additions/deletions. Confirm the comparison includes the release you intend to document and excludes unrelated work.

Then start generation. Review the draft for user-facing improvements, fixes and breaking changes. A code diff may show an implementation change without proving a customer-visible benefit, so avoid publishing an inferred promise without checking it.

Finalize the notes

Edit wording, add release context that you know to be true and verify any upgrade steps. Download the result, add it to a Space or share it using the available controls. Find the saved output later in Generations.

This workflow requires provider-backed branch comparison. A project ZIP is a one-time snapshot and does not supply that branch history.

If the diff looks wrong, return to the repository and branch choices before generating again.