[Feature flag] Cleanup prevent_visibility_restriction
Summary
This issue is to clean up the prevent_visibility_restriction
feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.
Introduced in !124649 (merged), the flag guarded the validation to prevent default project, group visibility being restricted, which can break the signup and registration flows. The feature will be productized.
Owners
- Team: Growth::Acquisition
- Most appropriate slack channel to reach out to:
#g_acquisition
- Best individual to reach out to: @rliu-gl
- PM: NAME
Cleaning up the feature flag
-
Specify in the issue description if this feature will be removed completely or will be productized as part of the Feature Flag cleanup -
Create a merge request to remove <feature-flag-name>
feature flag. Ask for review and merge it.-
Remove all references to the feature flag from the codebase. -
Remove the YAML definitions for the feature from the repository. -
Create a changelog entry.
-
-
Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post. -
/chatops run auto_deploy status <merge-commit-of-cleanup-mr>
-
-
Close the feature issue to indicate the feature will be released in the current milestone. -
If not already done, clean up the feature flag from all environments by running these chatops command in #production
channel:/chatops run feature delete <feature-flag-name> --dev --ops --pre --staging --staging-ref --production
-
Close this rollout issue.
Edited by Roy Liu