Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
25ba3ed5
Commit
25ba3ed5
authored
Feb 08, 2019
by
Shinya Maeda
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Apply suggestion to doc/user/project/operations/feature_flags.md
parent
6679c68f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
doc/user/project/operations/feature_flags.md
doc/user/project/operations/feature_flags.md
+1
-1
No files found.
doc/user/project/operations/feature_flags.md
View file @
25ba3ed5
...
...
@@ -63,7 +63,7 @@ and toggle the status for each scope.
In general, an application is deployed to multiple environments, such as
production, staging and
[
review apps
](
../../../ci/review_apps/index.md
)
.
You may not want to enable a feature flag on production until
QA team has
For example, you may not want to enable a feature flag on production until your
QA team has
first confirmed that the feature is working correctly on testing environments.
To define statuses for each environment:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment