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
de213342
Commit
de213342
authored
Sep 18, 2019
by
Winnie Hellmann
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify that IS_GITLAB_EE works for the whole GitLab now
parent
c12f6cdf
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
doc/development/ee_features.md
doc/development/ee_features.md
+1
-1
No files found.
doc/development/ee_features.md
View file @
de213342
...
...
@@ -19,7 +19,7 @@ CE specs should remain untouched as much as possible and extra specs
should be added for EE. Licensed features can be stubbed using the
spec helper
`stub_licensed_features`
in
`EE::LicenseHelpers`
.
You can force
Webpack
to act as CE by either deleting the
`ee/`
directory or by
You can force
GitLab
to act as CE by either deleting the
`ee/`
directory or by
setting the
[
`IS_GITLAB_EE` environment variable
](
https://gitlab.com/gitlab-org/gitlab/blob/master/config/helpers/is_ee_env.js
)
to something that evaluates as
`false`
. The same works for running tests
(for example
`IS_GITLAB_EE=0 yarn jest`
).
...
...
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