mirror of
https://github.com/github/gitignore
synced 2024-11-29 23:24:21 +01:00
dfce3fda43
The file `.byebug_history` is generated when using the popular https://github.com/deivid-rodriguez/byebug gem for debugging in Ruby. It contains a list of commands the user has run while debugging, which should not be committed to the repository. The author of the gem agrees with this here: https://github.com/deivid-rodriguez/byebug/issues/204#issuecomment-178238302
I have copied this from the Rails gitignore here: f908e51bcf/Rails.gitignore (L45)
54 lines
1.1 KiB
Plaintext
54 lines
1.1 KiB
Plaintext
*.gem
|
|
*.rbc
|
|
/.config
|
|
/coverage/
|
|
/InstalledFiles
|
|
/pkg/
|
|
/spec/reports/
|
|
/spec/examples.txt
|
|
/test/tmp/
|
|
/test/version_tmp/
|
|
/tmp/
|
|
|
|
# Used by dotenv library to load environment variables.
|
|
# .env
|
|
|
|
# Ignore Byebug command history file.
|
|
.byebug_history
|
|
|
|
## Specific to RubyMotion:
|
|
.dat*
|
|
.repl_history
|
|
build/
|
|
*.bridgesupport
|
|
build-iPhoneOS/
|
|
build-iPhoneSimulator/
|
|
|
|
## Specific to RubyMotion (use of CocoaPods):
|
|
#
|
|
# We recommend against adding the Pods directory to your .gitignore. However
|
|
# you should judge for yourself, the pros and cons are mentioned at:
|
|
# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
|
|
#
|
|
# vendor/Pods/
|
|
|
|
## Documentation cache and generated files:
|
|
/.yardoc/
|
|
/_yardoc/
|
|
/doc/
|
|
/rdoc/
|
|
|
|
## Environment normalization:
|
|
/.bundle/
|
|
/vendor/bundle
|
|
/lib/bundler/man/
|
|
|
|
# for a library or gem, you might want to ignore these files since the code is
|
|
# intended to run in multiple environments; otherwise, check them in:
|
|
# Gemfile.lock
|
|
# .ruby-version
|
|
# .ruby-gemset
|
|
|
|
# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
|
|
.rvmrc
|