diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-15 15:42:17 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-15 15:42:17 +0000 |
| commit | 44fdf983bd35328dd577d3d3650d14163ef3e2b6 (patch) | |
| tree | 84ff300d056cfbabb5a0fe2a9cbaa80aaeab1cc5 /doc/development/feature_flags/controls.md | |
| parent | bc9fa07b26184b5c94808f704db6ea1ac81bf4de (diff) | |
| download | gitlab-ce-44fdf983bd35328dd577d3d3650d14163ef3e2b6.tar.gz | |
Add latest changes from gitlab-org/gitlab@12-10-stable-ee
Diffstat (limited to 'doc/development/feature_flags/controls.md')
| -rw-r--r-- | doc/development/feature_flags/controls.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/development/feature_flags/controls.md b/doc/development/feature_flags/controls.md index fa9942e8d81..aa32285b27b 100644 --- a/doc/development/feature_flags/controls.md +++ b/doc/development/feature_flags/controls.md @@ -29,6 +29,11 @@ Monitor stage, Health group. For all production environment Chatops commands, use the `#production` channel. +As per the template, where a feature would have a (potentially) significant user +impact and the feature is being enabled instance wide prior to release, please copy +the Slack message and repost in the `#support_gitlab-com` channel for added visibility +and awareness, preferably with a link to the issue, MR, or docs. + Regardless of the channel in which the Chatops command is ran, any feature flag change that affects GitLab.com will automatically be logged in an issue. The issue is created in the [gl-infra/feature-flag-log](https://gitlab.com/gitlab-com/gl-infra/feature-flag-log/issues?scope=all&utf8=%E2%9C%93&state=closed) project, and it will at minimum log the Slack handle of person enabling a feature flag, the time, and the name of the flag being changed. |