Gaitro and GitLab merge trains, for code agents write
A merge train queues merge requests and tests each one together with the ones ahead of it, so the main branch stays green. Gaitro tests what ships in a similar way, and also tells agents about an overlap while they work, before there's anything to merge.
- The unit of work
Gaitro
A draft, opened from a request in plain words
GitLab merge trains
A merge request from a branch
- When agents would collide
Gaitro
As they edit: what each agent changes is reserved for it as it saves, function by function, so a second agent that touches it hears at once and waits its turn, or asks to go first
GitLab merge trains
When merge requests are merged, or when a pipeline on the combined result fails
- Testing changes together
Gaitro
Every change is checked merged with the published version before it ships, and shipping goes through a queue
GitLab merge trains
Each merge request's pipeline runs on its changes merged with the target branch and the merge requests ahead of it in the train
- When a change fails
Gaitro
It doesn't ship, and the draft says which check failed and why
GitLab merge trains
It leaves the train, and the merge requests behind it run their pipelines again
- Reviewing a change
Gaitro
A summary in plain words, what changed, and checks written as sentences
GitLab merge trains
Diffs, discussions and approval rules
- Tests
Gaitro
Checks are sentences; the agent writes each one's test; every run gets a fresh sandbox
GitLab merge trains
CI/CD pipelines you configure in .gitlab-ci.yml
- Going live
Gaitro
Nothing ships until a person presses Ship it; any earlier version comes back in one click
GitLab merge trains
Merging to the target branch, then whatever deploy your pipelines run
- Who it's for
Gaitro
People directing agents, whether or not they read code
GitLab merge trains
Teams of developers, and organizations using GitLab's wider platform
| Gaitro | GitLab merge trains | |
|---|---|---|
| The unit of work | A draft, opened from a request in plain words | A merge request from a branch |
| When agents would collide | As they edit: what each agent changes is reserved for it as it saves, function by function, so a second agent that touches it hears at once and waits its turn, or asks to go first | When merge requests are merged, or when a pipeline on the combined result fails |
| Testing changes together | Every change is checked merged with the published version before it ships, and shipping goes through a queue | Each merge request's pipeline runs on its changes merged with the target branch and the merge requests ahead of it in the train |
| When a change fails | It doesn't ship, and the draft says which check failed and why | It leaves the train, and the merge requests behind it run their pipelines again |
| Reviewing a change | A summary in plain words, what changed, and checks written as sentences | Diffs, discussions and approval rules |
| Tests | Checks are sentences; the agent writes each one's test; every run gets a fresh sandbox | CI/CD pipelines you configure in .gitlab-ci.yml |
| Going live | Nothing ships until a person presses Ship it; any earlier version comes back in one click | Merging to the target branch, then whatever deploy your pipelines run |
| Who it's for | People directing agents, whether or not they read code | Teams of developers, and organizations using GitLab's wider platform |
When GitLab merge trains is the better fit
Teams already on GitLab for planning, CI/CD, security scanning and the rest of its platform, with developers reviewing merge requests. Merge trains are a proven way to keep a busy main branch green.
When Gaitro is
When several agents work at once and you'd rather hear about an overlap while they edit than when a pipeline fails; when you want each change explained in plain words, checks written as sentences, and a person deciding what goes live.
Using both
Gaitro speaks Git, so a project can be cloned and kept in step with a copy on GitLab. Bring an existing repository in with gaitro init, history included.
GitLab is a trademark of GitLab Inc. Gaitro isn't affiliated with or endorsed by GitLab. Compared as of October 2026.