Skip to main content
November 4, 2026
A merged GitLab merge request with a Paradime Merge Run Summary note: Passed, the merge commit merged into main, and a table with the on_merge_build step, its status, duration, and a link to the run
Before this release, continuous deployment on GitLab needed a .gitlab-ci.yml job that called the Bolt API on your own runners. With the GitLab connection, Paradime starts your On Merge schedules itself when a merge request merges.
  • The right commit. The run uses the merge commit, or the squash commit if you squash. It keeps that commit even if more commits land on the branch while it runs.
  • One summary note. A Paradime Merge Run Summary note on the merged merge request links to each run and updates as the runs finish.
  • Several schedules in order. Chain on-merge schedules, or make merges take turns with a merge queue. See Chains.
Set the schedule’s Git branch to the branch your merge requests target, and its trigger to On Merge. See Continuous deployment on GitLab. Shipped in Paradime v6.24.0.