[Feature flag] Rollout of `allow_edit_commit_messages`
What
Remove the allow_edit_commit_messages
feature flag once the behavior has been deemed stable
Owners
- Team: teamDelivery
- Most appropriate slack channel to reach out to:
#g_delivery
- Best individual to reach out to:
@yorickpeterse
,@mayra-cabrera
Expectations
What are we expecting to happen?
Users should be able to edit their own commit messages on unprotected branches
What might happen if this goes wrong?
TBD
What can we monitor to detect problems with this?
TBD
Beta groups/projects
-
gitlab-org/gitlab
project
Roll Out Steps
-
Confirm that QA tests pass with the feature flag enabled (if you're unsure how, contact the relevant stable counterpart in the Quality department) -
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 the SRE oncall and release managers - In
#production
mention@sre-oncall
and@release-managers
. Once an SRE on call and Release Manager on call confirm, you can proceed with the rollout
- In
-
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
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set --project=gitlab-org/gitlab allow_edit_commit_messages false