feat: Add mention trigger by default for Duo Developer
What does this MR do and why?
Adds the mention trigger to the developer/v1 foundational flow definition so that Duo Developer automatically responds when mentioned in issues or MRs, without requiring users to manually configure this trigger.
Previously, the developer/v1 flow only had the assign trigger enabled by default. With the changes from #589246 (closed), Duo Developer can iterate on MR changes when mentioned — but users had to manually add the mention trigger to make this work.
This change adds mention alongside assign in the developer/v1 triggers array, so the mention trigger is automatically active for any Duo Developer, whether it was already activated or is newly added to a project.
The SyncFoundationalFlowsService already handles deduplication — it only creates triggers for event types that don't already exist — so existing Duo Developer installations will automatically get the mention trigger added on the next sync.
References
- Closes #593201 (closed)
- Related: #589246 (closed)
Screenshots or screen recordings
N/A — backend-only change.
| Before | After |
|---|---|
developer/v1 triggers: [assign] |
developer/v1 triggers: [assign, mention] |
How to set up and validate locally
- Open the GitLab Duo settings on a group that has DAP enabled, enable foundational flows and specifically the Duo Developer
- Open Triggers in a project in the group e.g. http://gdk.test:3000/free-tier/free-tier-project/-/automate/triggers
- Verify the triggers are added
- Mention the Duo Developer bot in an MR comment and verify it responds
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.