Cleanup edit_branch_rules feature flag

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

This issue is to cleanup the edit_branch_rules feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.

Owners

• Team: groupsource code
• Most appropriate slack channel to reach out to: #g_create_source-code
• Best individual to reach out to: @psjakubowska
• PM: @phikai

Stakeholders

Expectations

1. Remove Protected branches section in the Project / Settings / Repository. See Remove messaging regarding protected branches (#538383 - closed) for reference. This has already been completed, but had to be reverted due to Investigate dependency between Custom roles and... (#576364)
2. Update documentation on Protected branches and Branch rules
3. Remove all references to the feature flag from the codebase

What might happen if this goes wrong?

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 edit_branch_rules 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 edit_branch_rules --dev --pre --staging --staging-ref --production
• Close this rollout issue.