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
4aa1df68
Commit
4aa1df68
authored
Mar 05, 2021
by
Marcia Ramos
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify that every FF must be documented
parent
f4ef8ca3
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
0 deletions
+3
-0
doc/development/documentation/feature_flags.md
doc/development/documentation/feature_flags.md
+3
-0
No files found.
doc/development/documentation/feature_flags.md
View file @
4aa1df68
...
...
@@ -14,6 +14,9 @@ feature flag depends on its state (enabled or disabled). When the state
changes, the developer who made the change
**must update the documentation**
accordingly.
Every feature introduced to the codebase, even if it's behind a feature flag, must be documented.
For context, see the
[
latest merge request that updated this guideline
](
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/47917#note_459984428
)
.
## Criteria
According to the process of
[
deploying GitLab features behind feature flags
](
../feature_flags/process.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