Ruby .gitignore Template
Ruby installed gems, bundler cache, coverage reports, and documentation. Generated and merged deterministically with upstream GitHub repository patterns to keep your repository clean of package directories, temporary build artifacts, and local environment files.
Interactive Stack Generator
Preconfigured with RubyRuby installed gems, bundler cache, coverage reports, and documentation
### Ruby ###*.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_historybuild/*.bridgesupportbuild-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 # Used by RuboCop. Remote config files pulled in from inherit_from directive.# .rubocop-https?--* Raw Ruby .gitignore
Crawlable upstream source template*.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_historybuild/*.bridgesupportbuild-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 # Used by RuboCop. Remote config files pulled in from inherit_from directive.# .rubocop-https?--* Key Pattern Breakdown
Dependencies & Package Registries
External libraries and package manager directories installed locally rather than stored in version control.
Build Outputs & Compiled Artifacts
Generated binary files, compilation targets, and distribution bundles that can be reliably reproduced from source.
Execution Caches & Runtime Logs
Diagnostic logs, runtime metadata, test coverage reports, and incremental compiler caches that cause noisy repository diffs.
Source & Verification
Place this file in the root directory of your project as .gitignore. Changes take effect on newly added or untracked files.