Rollout: organization_read_only_enforcement feature flag

Rollout tracking issue for the organization_read_only_enforcement feature flag.

Part of &20404 (Implement Organizations Read-Only Mode). Design: ADR 010.

Flag

  • Name: organization_read_only_enforcement
  • Type: gitlab_com_derisk, default-off
  • Gates: write-blocking enforcement for organizations in read-only mode (controllers, REST API, GraphQL mutations, git push), introduced in #603366 (closed)
  • Scope: environment- and Organization-scoped, so rollout can proceed cohort-by-cohort

Rollout plan

  • Merge enforcement behind the flag (#603366 (closed)), default-off, verified dark — merged in !241161 (merged) (2026-06-24)
  • Enable for internal/test Organizations on GitLab.com
  • Expand alongside the existing Organizations rollout cohorts
  • Monitor structured errors / blocked-write logs and dashboards
  • Default-enable once confidence is reached
  • Remove the flag after GA

Notes

  • Default-off on Self-Managed and Dedicated (instance-wide Maintenance Mode remains the right tool there, see ADR 007).
  • Broader flag gating strategy is tracked in #602810.

Related:

Edited by Chen Zhang