Add ability to create feature flag from merge request through markdown (API)
Problem to solve
When developers ship a feature with a feature flag, they have to do two things manually, today.
- Merge a merge request which contains a new change behind a feature flag
- Create a feature flag which has the same name with the flag name in code. For example, in GitLab workflow, we execute a chatops command e.g.
/chatops run feature set <feature-name> <value>for creating a corresponding feature flag.
Proposal
Users can mention Create ^<FF-name> in MR description to create the feature flag when the merge request has been merged (Similar to Closing issue automatically). This way, users can manipulate feature flags altogether with the occurrences in the code base.
The created feature flag should be disabled for all environments by default. Later on, developers/operators can jump into the FF page or use API and manipulate the flag for A/B testing or such.
Related
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.