GitLab Feature Flags

3/26/2026

This post introduces and explains the technical implementation of GitLab's feature flags capability. It details how GitLab exposes an Unleash-compatible API, enabling the use of Unleash client SDKs for local flag evaluation. The post provides a practical guide using a Python Flask application and the Unleash Python SDK, covering setup, credential management, application logic for checking flags, and real-time toggling. It highlights the benefits of using the SDK over the REST API for performance and security.

8/16/2023

This post details the technical challenges and strategic decisions involved in merging a large integration branch for the Remote Development feature into the main GitLab `master` branch. It highlights the use of feature flags to enable a beta release, the management of a large merge request with extensive CI pipeline coverage, and the organization of follow-up tasks into child epics. It also touches upon the application security and database review processes.

2/12/2021

This post details UX work on improving feature flag management by proposing to treat feature flags as an issue type. This would allow users to manage feature flags in a centralized location and leverage existing issue capabilities like comments and threaded discussions. This is currently in solution validation with development work planned to start in 13.10.

8/6/2019

This post introduces the concept of Feature Flags as a key component of Progressive Delivery. It explains what feature flags are, categorizes them (release, experiment, ops, permission toggles), and discusses best practices for their implementation, including testing strategies and managing stale flags. It highlights the challenges of relying on external feature management systems and mentions GitLab's existing alpha feature flag capabilities for specific users and percent rollout per environment, with further functionality planned.