[FF] `merge_request_create_flow_trigger` -- Scoped to the Project level. If enabled, the created merge request trigger event is available and Developer flow runs start when a merge request is created.

Summary

Roll out the created merge request Duo Agent Platform flow trigger currently behind the merge_request_create_flow_trigger feature flag.

DRI: @marc_shaw
Team Slack channel: #g_dap_events

Note

Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. Feature flag controls · Feature flag lifecycle

What could go wrong?

Blast radius is every merge request creation on a project that has a merge_request flow trigger configured. No data-loss risk: the flag gates whether MergeRequests::PreparedCloudEvent is published at all, so with it off nothing is published, no worker is scheduled, and no Redis keys are written.

The flag exists primarily to satisfy Sidekiq compatibility across updates: Ai::Catalog::Flows::ExecuteMergeRequestPreparedWorkflowTriggersWorker is a brand new worker schedulable from an HTTP request, and GitLab.com has no Sidekiq canary stage, so without the flag it could be enqueued from canary hours before the Sidekiq fleet can run it.

Introduced by !242698 (merged).

Rollout

Run all production /chatops in #production and cross-post the results to #g_dap_events. Background: incremental rollout process, feature actors.

Non-production

/chatops gitlab run feature set merge_request_create_flow_trigger 50 --actors --dev --pre --staging --staging-ref
/chatops gitlab run feature set merge_request_create_flow_trigger true --dev --pre --staging --staging-ref

Production — percentage rollout (wait ≥15 min between steps, watch dashboards):

/chatops gitlab run feature set merge_request_create_flow_trigger <percentage> --actors

Or target specific actors instead:

/chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss merge_request_create_flow_trigger true
/chatops gitlab run feature set --group=gitlab-org,gitlab-com merge_request_create_flow_trigger true
/chatops gitlab run feature set --user=marc_shaw merge_request_create_flow_trigger true

Before global rollout

Confirm the relevant gotchas before going to 100% — see enabling a feature for GitLab.com:

Docs + version history updated
Breaking changes announced, if any
Change management issue opened, if required
External API consumers handled with a fail-open mechanism, if applicable

Cleanup

Remove the flag once deemed stable — see cleaning up. Track it here, or open a follow-up Feature Flag Cleanup issue. Remove the flag and its YAML definition from the codebase, then:

/chatops gitlab run release check <merge-request-url> <milestone>
/chatops gitlab run feature delete merge_request_create_flow_trigger --dev --pre --staging --staging-ref --production

Rollback

/chatops gitlab run feature set merge_request_create_flow_trigger false                                         # production
/chatops gitlab run feature set merge_request_create_flow_trigger false --dev --pre --staging --staging-ref     # non-production
/chatops gitlab run feature delete merge_request_create_flow_trigger --dev --pre --staging --staging-ref --production  # remove entirely

[FF] merge_request_create_flow_trigger -- Scoped to the Project level. If enabled, the created merge request trigger event is available and Developer flow runs start when a merge request is created.