## Summary This issue is to cleanup the `strip_signature_from_ci_commit_tag_message` feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production. ## Owners - Team: Create:Source Code - Most appropriate slack channel to reach out to: `#g_create_source-code` - Best individual to reach out to: @vyaklushin - PM: TBD ## Stakeholders ## Expectations ### 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 `strip_signature_from_ci_commit_tag_message` 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](https://docs.gitlab.com/ee/development/feature_flags/#changelog). - [ ] Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before [the code cutoff](https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-1), 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](https://gitlab.com/gitlab-org/gitlab/-/issues/583219) 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 strip_signature_from_ci_commit_tag_message --dev --pre --staging --staging-ref --production` - [ ] Close [the rollout issue](https://gitlab.com/gitlab-org/gitlab/-/issues/583733).