SUMMARIZATION

GitLab MR Changelog Draft Back into the Release MR

When a release-prep MR is opened, drafts customer-facing changelog entries from the MRs it bundles and posts them as a review comment for an editor to approve before tagging.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerRelease-prep MR openedGitLabGitLab
  • ActionFetch MRs staged for this releaseGitLabGitLab
  • LogicClassify each MR by type
  • ActionDraft per-category changelog with OpenAIOpenAI
  • OutputPost draft as review comment on the MRGitLabGitLab

What it does

Gives your release manager a ready-to-edit changelog draft inside the release-prep MR itself, so the human review happens before the version is ever tagged.

When to use it

Use it when changelog copy must be reviewed and edited by a person before publishing — common in regulated or brand-sensitive products where AI drafts assist but never auto-publish.

How it works

  1. 1Opening an MR labeled `release-prep` triggers the flow.
  2. 2GitLab is queried for the set of MRs staged for this release, including their descriptions and linked issues.
  3. 3A logic step classifies each MR as Feature, Fix, or Breaking Change based on labels and title conventions.
  4. 4OpenAI drafts a complete changelog section per category, flagging any breaking changes prominently.
  5. 5The draft is posted back as a comment on the release-prep MR, where an editor can revise and approve it before the release is tagged.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.