GitLab 19.0 Turns Merge Requests Into an Automated Workflow
AI made writing code dramatically faster. However, the work between opening a merge request and actually merging it has stayed almost entirely manual, until now.
GitLab 19.0 ships with a significantly expanded Developer Flow, turning what was once a series of manual developer tasks into a fully automated merge request workflow. The release includes autonomous merge conflict resolution, one-click rebase and merge, and an AI agent that participates across the entire MR lifecycle.
Developer Flow previously automated the setup work between “here’s what needs to be built” and “here’s an MR to review.” That was useful, but once the MR existed, iteration remained manual. GitLab 19.0 changes that entirely.
The updated Developer Flow now picks up from wherever it left off. Teams can trigger it from an issue using the Generate MR button, by assigning the Duo Developer service account directly to an issue or MR, or by using the new @mention trigger from any discussion thread. Crucially, the agent iterates on the same MR rather than producing a new one that requires reconciliation.
The agent handles the work that surrounds the code. It addresses reviewer feedback across multiple rounds, resolves merge conflicts on long-running branches, researches unfamiliar codebases, splits oversized MRs, and implements features from scratch. Under the hood, it runs as a single agentic loop with a full developer toolset, read, grep, edit, run commands, and decides for itself which action to use and when.
Project configuration also gets more powerful. AGENTS.md gives the agent non-obvious context: bash commands, conventions, environment quirks, and architectural decisions. Meanwhile, agent-config.yml sets up dependencies, tooling, and configuration so the agent runs tests and pre-commit hooks before committing. Together, they ensure the agent’s output matches team standards instead of creating rework.
Merge conflict resolution gets its own dedicated upgrade. The new Resolve with Duo button appears directly on the MR conflict page and the merge checks widget. The agent reads both branches, picks a resolution strategy, edits conflicting files, commits, and pushes the fix. It then leaves a comment summarizing what it found and how it resolved it. If the agent cannot safely resolve the conflict, it says so rather than guessing.
At the end of the MR lifecycle, one-click rebase and merge removes the final friction point. Teams using semi-linear history or fast-forward merge methods previously had to rebase, wait, return, and then merge. Now it is a single action. This feature is available across Free, Premium, and Ultimate tiers.
Developer Flow with the full agentic capabilities is available through GitLab Duo Agent Platform on Premium and Ultimate plans. GitLab Free tier users can also access it by following the sign-up steps for GitLab Duo Agent Platform.
Additionally, GitLab 19.0 ships alongside related releases, including more AI models for GitLab Duo Agent Platform Self-Hosted, Secrets Manager entering public beta, and CI component usage tracking.
The result is a fully automated merge request workflow where developers steer and review, while the agent handles execution from first commit to final merge.
