Add exception for gitlab_com_derisk feature flags

Vasilii Iakliushinrequested to merge
duo-edit-20251120-133427 into main

Based on feedback from gitlab-org/create-stage#13291 (comment 2899235993), this MR adds an exception for gitlab_com_derisk feature flags to the decision-making process documentation.

Changes

  • Added an exception paragraph to the "Launches of Feature Flag rollouts" section
  • gitlab_com_derisk type feature flags now only require an FYI to EM and PM, not explicit approval
  • This allows engineers to use their best judgment for stability purposes without being blocked

Context

The discussion concluded that gitlab_com_derisk flags are used as a safety net for deploying potentially risky changes to GitLab.com, and requiring explicit approval could delay mitigation of incidents or issues.

cc @andr3 for review as requested

Merge request reports