diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-05-10 00:09:33 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-05-10 00:09:33 +0000 |
| commit | fb214ec6e0c78f96781ac7889d6d86c88a824e90 (patch) | |
| tree | ec47404d3d813fd6b688679883a3145f413b6d2f /.gitlab/issue_templates | |
| parent | b558e1ad8f1d2d52e0c88ad712cd3d567cf52e10 (diff) | |
| download | gitlab-ce-fb214ec6e0c78f96781ac7889d6d86c88a824e90.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to '.gitlab/issue_templates')
| -rw-r--r-- | .gitlab/issue_templates/Feature Flag Cleanup.md | 2 | ||||
| -rw-r--r-- | .gitlab/issue_templates/Feature Flag Roll Out.md | 6 |
2 files changed, 6 insertions, 2 deletions
diff --git a/.gitlab/issue_templates/Feature Flag Cleanup.md b/.gitlab/issue_templates/Feature Flag Cleanup.md index eedb35a4b5f..7e0462a5cba 100644 --- a/.gitlab/issue_templates/Feature Flag Cleanup.md +++ b/.gitlab/issue_templates/Feature Flag Cleanup.md @@ -41,7 +41,7 @@ Are there any other stages or teams involved that need to be kept in the loop? 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](ISSUE LINK) to indicate the feature will be released in the current milestone. -- [ ] Clean up the feature flag from all environments by running these chatops command in `#production` channel: +- [ ] 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` - [ ] `/chatops run feature delete <feature-flag-name> --staging` - [ ] `/chatops run feature delete <feature-flag-name>` diff --git a/.gitlab/issue_templates/Feature Flag Roll Out.md b/.gitlab/issue_templates/Feature Flag Roll Out.md index 0462742513c..910ec01a49c 100644 --- a/.gitlab/issue_templates/Feature Flag Roll Out.md +++ b/.gitlab/issue_templates/Feature Flag Roll Out.md @@ -123,6 +123,10 @@ To do so, follow these steps: If the merge request was deployed before [the monthly release was tagged](https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-1), the feature can be officially announced in a release blog post. - [ ] `/chatops run release check <merge-request-url> <milestone>` +- [ ] Consider cleaning up the feature flag from all environments by running these chatops command in `#production` channel. Otherwise these settings may override the default enabled. + - [ ] `/chatops run feature delete <feature-flag-name> --dev` + - [ ] `/chatops run feature delete <feature-flag-name> --staging` + - [ ] `/chatops run feature delete <feature-flag-name>` - [ ] Close [the feature issue](ISSUE LINK) to indicate the feature will be released in the current milestone. - [ ] Set the next milestone to this rollout issue for scheduling [the flag removal](#release-the-feature). - [ ] (Optional) You can [create a separate issue](https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Feature%20Flag%20Cleanup) for scheduling the steps below to [Release the feature](#release-the-feature). @@ -157,7 +161,7 @@ You can either [create a follow-up issue for Feature Flag Cleanup](https://gitla the feature can be officially announced in a release blog post. - [ ] `/chatops run release check <merge-request-url> <milestone>` - [ ] Close [the feature issue](ISSUE LINK) to indicate the feature will be released in the current milestone. -- [ ] Clean up the feature flag from all environments by running these chatops command in `#production` channel: +- [ ] 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` - [ ] `/chatops run feature delete <feature-flag-name> --staging` - [ ] `/chatops run feature delete <feature-flag-name>` |