Draft release notes with Git2log

Git2log turns pasted commit messages into proposed changelog posts. It does not continuously sync your repository or establish that a commit has been deployed.

Prepare the source

Ask a developer for the commits included in the release. For example, this command lists recent commits:

git log --oneline --since="2 weeks ago"

Review the list before copying it. Remove work that has not shipped, internal details and changes that do not need a customer announcement. Use up to 30 commit lines per generation.

Generate and review

  1. Open /admin/git2log on your portal.
  2. Paste the commit messages and generate the changelog.
  3. Review the proposed posts in the bulk creation screen.
  4. Correct titles, descriptions, categories and statuses. Explain the customer-visible result where a commit message is too technical.
  5. Confirm the posts you want to create.

Each generation uses one AI credit. The tool proposes content from your input, so check it against what actually shipped.

For one release note covering several changes, combine roadmap items in a changelog entry. Review subscriber notification settings before publishing.