Q1 Post-Rearch Triggers Implementation
## Release notes You can now configure event-based triggers to automatically invoke Duo Flows and agents in response to GitLab events — without any manual intervention. Supported trigger events include: - **Pipeline failed** — automatically attempt to fix a failing pipeline. - **MR created** — kick off a flow when a new merge request is opened. - **MR approved** — run automation after a merge request is approved. - **Merge conflict detected** — respond to code conflicts as they arise. - **Draft → Ready for review** — trigger a flow when a draft MR is marked ready. - **Security scan completed** and **security policy violations detected** — automate security response workflows. - **Scheduled / cron** — run flows on a time-based schedule. - **External webhook** — invoke flows from any external system. Configure triggers in **AI > Triggers** within your project. https://docs.gitlab.com/user/duo_agent_platform/triggers/ Goal: Webhook/Event bridge to invoke agents and flows in order to automate value (e.g. trigger Fix Pipeline when a pipeline fails, and 55% of our pipelines fail!) TODO: * Discovery: What is current state today? What are our different event types? What work has already started or exists? * Requirements Gathering: https://gitlab.com/groups/gitlab-org/-/work_items/20229+ (better link TBD) * Customer-facing API with schema validation * Triggers for 5-10 events and easy additions * https://docs.google.com/spreadsheets/d/1bL6q1h8N1bqWuRIcyfvBTovYVSEK0oQmfsLNnOlfMU0/edit?gid=727875676#gid=727875676 * Collaborate: https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/18106+ (and with security) * Invest: Borrow / sub-team for \~4 engineers for a period of 2 milestones *
epic