Rollout the `:consolidated_edit_button` feature flag
What
Remove the :consolidated_edit_button
feature flag ...
Owners
- Team: devopscreate ~"group::editor"
- Most appropriate slack channel to reach out to:
#g_create_editor
- Best individual to reach out to: @himkp
Expectations
We consolidated the Edit and Web IDE buttons, where Web IDE is the default option, to encourage more usage of the Web IDE over single file editor.
Issue: #221247 (closed)
What are we expecting to happen?
We expect people to give feedback on the change if they don't like it.
What might happen if this goes wrong?
If there is substantial negative feedback about this feature, we could consider making "Edit" the default option in the dropdown, or removing the dropdown completely.
Beta groups/projects
-
gitlab-org
/gitlab-com
groups
Roll Out Steps
-
Enable on staging ( /chatops run feature set feature_name true --staging
) -
Test on staging -
Ensure that documentation has been updated -
Enable on GitLab.com for individual groups/projects listed above and verify behaviour ( /chatops run feature set --project=gitlab-org/gitlab feature_name true
) -
Coordinate a time to enable the flag with #production
and#g_delivery
on slack. -
Announce on the issue an estimated time this will be enabled on GitLab.com -
Enable on GitLab.com by running chatops command in #production
(/chatops run feature set feature_name true
) -
Cross post chatops Slack command to #support_gitlab-com
(more guidance when this is necessary in the dev docs) and in your team channel -
Announce on the issue that the flag has been enabled -
Remove feature flag and add changelog entry -
After the flag removal is deployed, clean up the feature flag by running chatops command in #production
channel
Edited by David O'Regan