Duo bug: Incorrectly batching multiple changes into one commit

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Earlier today, I asked DAP to update gitlab-com/runbooks!9735 (merged) with a new commit to fix the markdownlint pipeline errors.

Steps to reproduce

I have not officially reproduced it outside of this MR, but here's what I consistently found to be the case:

  1. Ask Duo to make multiple changes to the same file and push a commit.
  2. Duo makes only one change.

Example Project

What is the current bug behavior?

Instead of creating one commit to fix the three errors, it created one commit over all.

Screenshot_2025-11-27_at_4.04.44_PM

That became this commit: gitlab-com/runbooks!9735 (9c834706)

What is the expected correct behavior?

Duo creates one commit with all the changes.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by 🤖 GitLab Bot 🤖