Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,839
    • Issues 43,839
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,385
    • Merge requests 1,385
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #33394
Closed
Open
Created Oct 04, 2019 by Shinya Maeda@shinya.maeda💡Maintainer

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.

  1. Merge a merge request which contains a new change behind a feature flag
  2. 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

  • #30228 (closed)
  • #26456 (closed)
Edited Jul 05, 2020 by Orit Golowinski
Assignee
Assign to
Time tracking