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
ac995c41
Commit
ac995c41
authored
Oct 14, 2019
by
Evan Read
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add PM review and approval note
parent
c14a9077
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
0 deletions
+4
-0
doc/development/documentation/styleguide.md
doc/development/documentation/styleguide.md
+4
-0
No files found.
doc/development/documentation/styleguide.md
View file @
ac995c41
...
...
@@ -1065,6 +1065,10 @@ When documenting feature flags for a feature, it's important that users know:
-
That administrative access is required to make a feature flag change.
-
What to ask for when requesting a change to a feature flag's state.
NOTE:
**Note:**
The
[
Product Manager for the relevant group
](
https://about.gitlab.com/handbook/product/categories/#devops-stages
)
must review and approve product documentation involving feature flags.
The following is sample text for adding feature flag documentation for a feature:
````
md
...
...
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