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
0
Merge Requests
0
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
Tatuya Kamada
gitlab-ce
Commits
204020fc
Commit
204020fc
authored
Jan 27, 2017
by
Adam Niedzielski
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document "No gems fetched from git repositories" policy [ci skip]
parent
305270e8
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
15 additions
and
0 deletions
+15
-0
doc/development/README.md
doc/development/README.md
+1
-0
doc/development/gemfile.md
doc/development/gemfile.md
+14
-0
No files found.
doc/development/README.md
View file @
204020fc
...
...
@@ -18,6 +18,7 @@
-
[
Frontend guidelines
](
frontend.md
)
-
[
SQL guidelines
](
sql.md
)
for working with SQL queries
-
[
Sidekiq guidelines
](
sidekiq_style_guide.md
)
for working with Sidekiq workers
-
[
`Gemfile` guidelines
](
gemfile.md
)
## Process
...
...
doc/development/gemfile.md
0 → 100644
View file @
204020fc
# `Gemfile` guidelines
When adding a new entry to
`Gemfile`
or upgrading an existing dependency pay
attention to the following rules.
## No gems fetched from git repositories
We do not allow gems that are fetched from git repositories. All gems have
to be available in the RubyGems index. We want to minimize external build
dependencies and build times.
## License compliance
Refer to
[
licensing guidelines
](
licensing.md
)
for ensuring license compliance.
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