-
Notifications
You must be signed in to change notification settings - Fork 2
/
.gitignore
30 lines (27 loc) · 991 Bytes
/
.gitignore
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
/.bundle/
/.yardoc
/_yardoc/
/coverage/
/doc/
/pkg/
/spec/reports/
/tmp/
# rspec failure tracking
.rspec_status
.byebug_history
# https://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/
# Yehuda says we should not put the Gemfile.lock in version control
# when developing gems:
#
# This is also why we recommend that people do not check in their
# Gemfile.lock files in gem development. That file is emitted by
# bundler, and guarantees that all gems, including dependencies of
# dependencies, remain the same.
# However, when doing gem development, you want to know immediately
# when some change in the overall ecosystem breaks your setup. While
# you may want to insist on using a particular gem from its git
# location, you do not want to hardcode your development to a very
# specific set of gems, only to find out later that a gem released
# after you ran bundle install, but compatible with your version
# range, doesn't work with your code.
Gemfile.lock