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
28efe2dc
Commit
28efe2dc
authored
Nov 24, 2020
by
Jan Provaznik
Committed by
Mike Jang
Nov 24, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify adding of a new flag
parent
3f577ec0
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
1 deletion
+2
-1
doc/development/feature_flags/process.md
doc/development/feature_flags/process.md
+2
-1
No files found.
doc/development/feature_flags/process.md
View file @
28efe2dc
...
...
@@ -32,7 +32,8 @@ should be leveraged:
requests, you can use the following workflow:
1.
[
Create a new feature flag
](
development.md#create-a-new-feature-flag
)
which is
**off**
by default, in the first merge request.
which is
**off**
by default, in the first merge request which uses the flag.
Flags
[
should not be added separately
](
development.md#risk-of-a-broken-master-main-branch
)
.
1.
Submit incremental changes via one or more merge requests, ensuring that any
new code added can only be reached if the feature flag is
**on**
.
You can keep the feature flag enabled on your local GDK during development.
...
...
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