GitHub / guard/guard-bundler issues and pull requests
#45 - Fix compatibility issue with ruby 3.2
Pull Request -
State: closed - Opened by edouard over 2 years ago
#44 - Support for Ruby 3.2
Issue -
State: open - Opened by boof over 2 years ago
- 1 comment
#43 - Bump VERSION to 3.0.0
Pull Request -
State: closed - Opened by rymai over 5 years ago
- 1 comment
#42 - Depend on Ruby >= 2.4.9
Pull Request -
State: closed - Opened by rymai over 5 years ago
- 1 comment
#41 - Depend on Bundler >= 2.1 and fix deprecations
Pull Request -
State: closed - Opened by rymai over 5 years ago
#40 - `Bundler.with_clean_env` has been deprecated
Issue -
State: closed - Opened by UrsaDK over 5 years ago
#39 - Is there any support for gemsets?
Issue -
State: open - Opened by coaxial over 6 years ago
#38 - Bump VERSION to 2.2.1
Pull Request -
State: closed - Opened by rymai over 6 years ago
#37 - Restrict bundler's dependency with < 3
Pull Request -
State: closed - Opened by rymai over 6 years ago
#36 - Bump VERSION to 2.2.0
Pull Request -
State: closed - Opened by rymai over 6 years ago
#35 - Relax bundler dependency to >= 1.3.0
Pull Request -
State: closed - Opened by rymai over 6 years ago
- 4 comments
#34 - Bundler 2.x Compatibility
Issue -
State: closed - Opened by reidab over 6 years ago
- 1 comment
#33 - Default config doesn't monitor `Gemfile.lock`
Issue -
State: closed - Opened by andyw8 over 6 years ago
- 1 comment
#32 - Problems using with bundler > 1.12
Issue -
State: closed - Opened by fernandes about 9 years ago
- 17 comments
#31 - switch to container arch on Travis
Pull Request -
State: closed - Opened by e2 almost 10 years ago
- 1 comment
#30 - watch Gemfile.lock too
Pull Request -
State: closed - Opened by timoschilling almost 10 years ago
- 2 comments
#29 - Not working when directories set in Guardfile and Gemfile symlinked
Issue -
State: closed - Opened by deivid-rodriguez about 10 years ago
- 2 comments
#28 - Detect unwatched gemfile
Pull Request -
State: closed - Opened by e2 over 10 years ago
- 2 comments
#27 - bump guard-compat dep to 1.0
Pull Request -
State: closed - Opened by e2 over 10 years ago
- 1 comment
#26 - Use guard compat
Pull Request -
State: closed - Opened by e2 over 10 years ago
- 2 comments
#25 - option to run bundler with --binstubs
Issue -
State: closed - Opened by rolandjitsu over 11 years ago
- 2 comments
#24 - Display info before doing stuff
Issue -
State: closed - Opened by jmuheim over 11 years ago
- 2 comments
#23 - Update guard-bundler.gemspec
Pull Request -
State: closed - Opened by vkrishnasatya almost 12 years ago
- 3 comments
#22 - Update guard-bundler.gemspec
Pull Request -
State: closed - Opened by vkrishnasatya almost 12 years ago
- 1 comment
#21 - Update guard-bundler.gemspec
Pull Request -
State: closed - Opened by vkrishnasatya almost 12 years ago
- 1 comment
#20 - v2.0
Pull Request -
State: closed - Opened by rymai almost 12 years ago
- 13 comments
#19 - Bundle Install Fails on Guard ~> 1.1 Dependency
Issue -
State: closed - Opened by demisx almost 12 years ago
- 2 comments
#18 - Bundle Install for Different Rubies Using RVM
Issue -
State: closed - Opened by dnunez24 almost 12 years ago
- 3 comments
#17 - Update .travis.yml - allow failures on ruby-head
Pull Request -
State: closed - Opened by cablegram almost 12 years ago
- 1 comment
#16 - Fix grammar in Guardfile template.
Pull Request -
State: closed - Opened by Gaelan almost 12 years ago
- 1 comment
#15 - `bundle check` does more than just check the bundle -- it can update Gemfile.lock
Pull Request -
State: closed - Opened by cablegram almost 12 years ago
- 2 comments
#14 - Remove notification when the bundle is already up to date
Pull Request -
State: closed - Opened by cablegram almost 12 years ago
- 1 comment
#13 - Fix deprications: s/Config/RbConfig/ and s/.stub!/.stub/
Pull Request -
State: closed - Opened by cablegram almost 12 years ago
#12 - Made notifications terms correct: It's bundle install, not update
Pull Request -
State: closed - Opened by colszowka about 13 years ago
- 1 comment
#11 - Guard v1.1 deprecation warnings
Issue -
State: closed - Opened by docwhat about 13 years ago
- 4 comments
#10 - Updated to use Guard v1.1 without deprecation warnings.
Pull Request -
State: closed - Opened by josin about 13 years ago
- 2 comments
#9 - Advice to use bundle exec incompatible with guard-bundler
Issue -
State: closed - Opened by guyboltonking over 13 years ago
- 4 comments
#8 - Doesn’t install git Gem dependencies automatically
Issue -
State: closed - Opened by gerrit over 13 years ago
- 1 comment
#7 - Doesn't work with 3.1?
Issue -
State: closed - Opened by RobertDeRose almost 14 years ago
- 14 comments
#6 - Binstubs
Pull Request -
State: closed - Opened by thermistor almost 14 years ago
- 4 comments
#5 - Pausing with Guard?
Issue -
State: closed - Opened by lancejpollard about 14 years ago
- 1 comment
#4 - Doesn't run bundler when gemfile is changed.
Issue -
State: closed - Opened by msolovyov about 14 years ago
- 3 comments
#3 - bundle exec fix
Pull Request -
State: closed - Opened by hoverlover over 14 years ago
#2 - Could not find gem 'xxx (>= 0, runtime)' in any of the gem sources listed in your Gemfile.
Issue -
State: closed - Opened by hoverlover over 14 years ago
- 23 comments
#1 - Prevent fsevent_watch launch on OS X
Issue -
State: closed - Opened by thibaudgg almost 15 years ago
- 1 comment
Labels: darwin, tips