Skip to content
GitLab
Next
Closed
Issue created by Mycroft Kang@TaehyeokKangContributor10 of 12 checklist items completed10/12 checklist items

[Feature flag] Rollout of `allow_force_push_to_protected_branches`

What

Remove the allow_force_push_to_protected_branches feature flag

Introduced in !55261 (merged)

Owners

  • Team: groupsource code
  • Most appropriate slack channel to reach out to: #g_create_source-code-be
  • Best individual to reach out to: @vyaklushin

Expectations

What are we expecting to happen?

Feature flag enables a new toggle on protected branches page to allow force push.

image

What might happen if this goes wrong?

Users won't be able to force push changes to protected branches.

What can we monitor to detect problems with this?

Beta groups/projects

If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.

  • vyaklushin/www-gitlab-com project

Roll Out Steps

  • Enable on staging (/chatops run feature set allow_force_push_to_protected_branches true --staging)
  • Test on staging
  • Ensure that documentation has been updated (!55751 (diffs))
  • Enable on GitLab.com for individual groups/projects listed above and verify behaviour (/chatops run feature set --project=vyaklushin/www-gitlab-com allow_force_push_to_protected_branches 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
  • 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 allow_force_push_to_protected_branches 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. Ensure that the feature flag definition YAML file has been removed in the same MR that is removing the feature flag from the code
  • 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 allow_force_push_to_protected_branches false
Edited by Vasilii Iakliushin