thought-driven / bummr Goto Github PK
View Code? Open in Web Editor NEWUpdate your gems in separate commits. Identify any that fail your build.
License: MIT License
Update your gems in separate commits. Identify any that fail your build.
License: MIT License
I see from #7 and #11 that bummr used to update all possible dependencies, not just those in the Gemfile, but this was changed. I'd love it if this could be added back as an option — currently I use bummr to update all of my Gemfile dependencies, but then have to go through the process manually for the Gemfile.lock-only dependencies.
This must be a bug?
$ bummr update
To run Bummr, you must:
- Be in the root path of a clean git branch off of master
- Have no commits or local changes
- Have a 'log' directory, where we can place logs
- Have your build configured to fail fast (recommended)
- Have locked any Gem version that you don't wish to update in your Gemfile
- It is recommended that you lock your versions of `ruby` and `rails in your Gemfile`
Your test command is: 'bundle exec rake'
Are you ready to use Bummr? (y/n) y
There is no log directory or you are not in the root
/Users/yegor/.rvm/gems/ruby-2.3.3/gems/bummr-0.2.0/lib/bummr/check.rb:17:in `check': undefined method `yes?' for #<Bummr::Check:0x007fb69644b8b8> (NoMethodError)
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/bummr-0.2.0/lib/bummr/cli.rb:10:in `check'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/bummr-0.2.0/lib/bummr/cli.rb:18:in `update'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/thor-0.19.4/lib/thor/command.rb:27:in `run'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/thor-0.19.4/lib/thor/base.rb:444:in `start'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/bummr-0.2.0/bin/bummr:4:in `<top (required)>'
from /Users/yegor/.rvm/gems/ruby-2.3.3/bin/bummr:22:in `load'
from /Users/yegor/.rvm/gems/ruby-2.3.3/bin/bummr:22:in `<main>'
from /Users/yegor/.rvm/gems/ruby-2.3.3/bin/ruby_executable_hooks:15:in `eval'
from /Users/yegor/.rvm/gems/ruby-2.3.3/bin/ruby_executable_hooks:15:in `<main>
Can a failing exit code be added if bummr update/test
finds a failure?
We're adding bummr as a scheduled job (using HEADLESS) to keep an eye out for braking changes, and currently that job always passes because bummr doesn't return a failing code.
Thanks for the great work.
I would love to use this for my project. However, we use git workflow hooks for pre-commit
. One of our hooks will check the format of the commit message. The standard bummr
commit message fails this check and rejects the commit.
This can easily be avoided by skipping any pre-commit
hooks:
git commit -am 'message' --no-verify
.
I can create a PR with a change that allows this, but I just wanted to gauge whether this would be accepted? I think I would follow your previous use of ENV
vars (ie BUMMR_TEST
and BASE_BRANCH
).
Hello there
You don't have a license on this repo which might scare away most folks from adopting/incorporating. A license like MIT is probably sufficient for this repo.
Best
Balki
http://www.balki.io
It would be great if we could pass an option or ENV var to use a different branch than master for the base branch.
I'm trying to run bummr update
:
Bundle complete! 17 Gemfile dependencies, 67 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.
/Users/yegor/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:199:in `spawn': No such file or directory - bundle outdated (Errno::ENOENT)
from /Users/yegor/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:199:in `popen_run'
from /Users/yegor/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:147:in `popen2'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/bummr-0.1.8/lib/bummr/outdated.rb:14:in `outdated_gems'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/bummr-0.1.8/lib/bummr/cli.rb:23:in `update'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/thor-0.19.4/lib/thor/command.rb:27:in `run'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/thor-0.19.4/lib/thor/base.rb:444:in `start'
from /Users/yegor/.rvm/gems/ruby-2.3.3/gems/bummr-0.1.8/bin/bummr:4:in `<top (required)>'
from /Users/yegor/.rvm/gems/ruby-2.3.3/bin/bummr:22:in `load'
from /Users/yegor/.rvm/gems/ruby-2.3.3/bin/bummr:22:in `<main>'
from /Users/yegor/.rvm/gems/ruby-2.3.3/bin/ruby_executable_hooks:15:in `eval'
from /Users/yegor/.rvm/gems/ruby-2.3.3/bin/ruby_executable_hooks:15:in `<main>'
@lpender can you help?
In my Gemfile I've locked down a lot of my gems to minor updates only, when running your bummr update
command the commit message includes the most recent version of that gem instead of the version bummr updated that gem to.
eg:
For the paperclip gem I have the following in my Gemfile
gem 'paperclip', '~> 3.0'
When bummr updates it it takes it from 3.4.1 to 3.5.4, which is good, but it makes the commit message;
paperclip, {3.4.1 -> 4.3.6}
This is incorrect.
Thanks for this very useful tool.
When I update gems, I usually only update the ones listed in the Gemfile, which is what Gemnasium uses to report outdated gems. I noticed that bummr uses Bundler.load.specs
, which lists a whole lot more than what's in the Gemfile, and in some cases gems that aren't even in the . Is there a particular reason for that decision?Gemfile.lock
Would it be possible to provide some sort of configuration to allow the user to choose to update only the gems listed in the Gemfile?
Updating only the files listed in the Gemfile should automatically update the dependencies of those gems, and should make bummr run faster since the list of gems it iterates through will be smaller.
Thanks!
For example, I have the following commit messages:
Update redis from 3.2.2 to 0.6.1
Update sass from 3.4.21 to 3.3.6
The to
version number should be higher but it's lower in these cases.
When trying to update my gemfile I get this error.
.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bummr-0.5.0/lib/bummr/updater.rb:48:in rescue in updated_version_for': uninitialized constant Bummr::Updater::Error (NameError)`
The exception happens on https://github.com/lpender/bummr/blob/master/lib/bummr/updater.rb#L45
where the Error
is called but was never defined.
Gemfile:
# frozen_string_literal: true
source 'https://rubygems.org'
git_source(:github) { |repo| "https://github.com/#{repo}.git" }
ruby '~> 2.5.1'
# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', ['~> 5.2.1', '!=5.2.1.1']
# Use sqlite3 as the database for Active Record
gem 'pg'
# Use Puma as the app server
gem 'puma', '~> 3.11'
# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
# gem 'jbuilder', '~> 2.5'
# Use Redis adapter to run Action Cable in production
# gem 'redis', '~> 4.0'
# Use ActiveModel has_secure_password
# gem 'bcrypt', '~> 3.1.7'
# Use ActiveStorage variant
# gem 'mini_magick', '~> 4.8'
# Use Capistrano for deployment
# gem 'capistrano-rails', group: :development
# Reduces boot times through caching; required in config/boot.rb
gem 'bootsnap', '>= 1.1.0', require: false
# Use Rack CORS for handling Cross-Origin Resource Sharing (CORS), making cross-origin AJAX possible
# gem 'rack-cors'
#
gem 'aws-sdk-s3', require: false
gem 'fast_jsonapi'
gem 'health_check'
gem 'quandl-config'
gem 'redcarpet'
gem 'sentry-raven'
## Improve the admin panel
gem 'active_material'
gem 'activeadmin'
gem 'clearance'
gem 'mini_magick'
gem 'sass-rails'
group :debug do
# Call 'byebug' anywhere in the code to stop execution and get a debugger console
gem 'byebug', platforms: %i[mri mingw x64_mingw]
end
group :development do
gem 'listen', '>= 3.0.5', '< 3.2'
# Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
end
group :test, :ci do
gem 'factory_bot_rails'
gem 'faker'
gem 'rails-controller-testing'
gem 'rspec-rails'
gem 'shoulda-matchers', '4.0.0.rc1'
gem 'simplecov', require: false
end
Gemfile.lock
GEM
remote: https://rubygems.org/
specs:
actioncable (5.2.3)
actionpack (= 5.2.3)
nio4r (~> 2.0)
websocket-driver (>= 0.6.1)
actionmailer (5.2.3)
actionpack (= 5.2.3)
actionview (= 5.2.3)
activejob (= 5.2.3)
mail (~> 2.5, >= 2.5.4)
rails-dom-testing (~> 2.0)
actionpack (5.2.3)
actionview (= 5.2.3)
activesupport (= 5.2.3)
rack (~> 2.0)
rack-test (>= 0.6.3)
rails-dom-testing (~> 2.0)
rails-html-sanitizer (~> 1.0, >= 1.0.2)
actionview (5.2.3)
activesupport (= 5.2.3)
builder (~> 3.1)
erubi (~> 1.4)
rails-dom-testing (~> 2.0)
rails-html-sanitizer (~> 1.0, >= 1.0.3)
active_material (1.4.2)
activeadmin (1.4.3)
arbre (>= 1.1.1)
coffee-rails
formtastic (~> 3.1)
formtastic_i18n
inherited_resources (>= 1.9.0)
jquery-rails (>= 4.2.0)
kaminari (>= 0.15)
railties (>= 4.2, < 5.3)
ransack (>= 1.8.7)
sass (~> 3.1)
sprockets (< 4.1)
activejob (5.2.3)
activesupport (= 5.2.3)
globalid (>= 0.3.6)
activemodel (5.2.3)
activesupport (= 5.2.3)
activerecord (5.2.3)
activemodel (= 5.2.3)
activesupport (= 5.2.3)
arel (>= 9.0)
activestorage (5.2.3)
actionpack (= 5.2.3)
activerecord (= 5.2.3)
marcel (~> 0.3.1)
activesupport (5.2.3)
concurrent-ruby (~> 1.0, >= 1.0.2)
i18n (>= 0.7, < 2)
minitest (~> 5.1)
tzinfo (~> 1.1)
arbre (1.1.1)
activesupport (>= 3.0.0)
arel (9.0.0)
aws-eventstream (1.0.2)
aws-partitions (1.148.0)
aws-sdk-core (3.48.3)
aws-eventstream (~> 1.0, >= 1.0.2)
aws-partitions (~> 1.0)
aws-sigv4 (~> 1.1)
jmespath (~> 1.0)
aws-sdk-kms (1.16.0)
aws-sdk-core (~> 3, >= 3.48.2)
aws-sigv4 (~> 1.1)
aws-sdk-s3 (1.36.0)
aws-sdk-core (~> 3, >= 3.48.2)
aws-sdk-kms (~> 1)
aws-sigv4 (~> 1.0)
aws-sigv4 (1.1.0)
aws-eventstream (~> 1.0, >= 1.0.2)
bcrypt (3.1.12)
bootsnap (1.4.2)
msgpack (~> 1.0)
builder (3.2.3)
byebug (11.0.1)
clearance (1.17.0)
actionmailer (>= 3.1)
activemodel (>= 3.1)
activerecord (>= 3.1)
bcrypt
email_validator (~> 1.4)
railties (>= 3.1)
coffee-rails (4.2.2)
coffee-script (>= 2.2.0)
railties (>= 4.0.0)
coffee-script (2.4.1)
coffee-script-source
execjs
coffee-script-source (1.12.2)
concurrent-ruby (1.1.5)
crass (1.0.4)
diff-lcs (1.3)
docile (1.3.1)
email_validator (1.6.0)
activemodel
erubi (1.8.0)
execjs (2.7.0)
factory_bot (5.0.2)
activesupport (>= 4.2.0)
factory_bot_rails (5.0.1)
factory_bot (~> 5.0.0)
railties (>= 4.2.0)
faker (1.9.3)
i18n (>= 0.7)
faraday (0.15.4)
multipart-post (>= 1.2, < 3)
fast_jsonapi (1.5)
activesupport (>= 4.2)
ffi (1.10.0)
formtastic (3.1.5)
actionpack (>= 3.2.13)
formtastic_i18n (0.6.0)
globalid (0.4.2)
activesupport (>= 4.2.0)
has_scope (0.7.2)
actionpack (>= 4.1)
activesupport (>= 4.1)
health_check (3.0.0)
railties (>= 5.0)
i18n (1.6.0)
concurrent-ruby (~> 1.0)
inherited_resources (1.9.0)
actionpack (>= 4.2, < 5.3)
has_scope (~> 0.6)
railties (>= 4.2, < 5.3)
responders
jmespath (1.4.0)
jquery-rails (4.3.3)
rails-dom-testing (>= 1, < 3)
railties (>= 4.2.0)
thor (>= 0.14, < 2.0)
json (2.2.0)
kaminari (1.1.1)
activesupport (>= 4.1.0)
kaminari-actionview (= 1.1.1)
kaminari-activerecord (= 1.1.1)
kaminari-core (= 1.1.1)
kaminari-actionview (1.1.1)
actionview
kaminari-core (= 1.1.1)
kaminari-activerecord (1.1.1)
activerecord
kaminari-core (= 1.1.1)
kaminari-core (1.1.1)
listen (3.1.5)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
ruby_dep (~> 1.2)
loofah (2.2.3)
crass (~> 1.0.2)
nokogiri (>= 1.5.9)
mail (2.7.1)
mini_mime (>= 0.1.1)
marcel (0.3.3)
mimemagic (~> 0.3.2)
method_source (0.9.2)
mimemagic (0.3.3)
mini_magick (4.9.2)
mini_mime (1.0.1)
mini_portile2 (2.4.0)
minitest (5.11.3)
msgpack (1.2.9)
multipart-post (2.0.0)
nio4r (2.3.1)
nokogiri (1.10.3)
mini_portile2 (~> 2.4.0)
pg (1.1.4)
puma (3.12.1)
quandl-config (1.0.0)
activesupport
rack (2.0.7)
rack-test (1.1.0)
rack (>= 1.0, < 3)
rails (5.2.3)
actioncable (= 5.2.3)
actionmailer (= 5.2.3)
actionpack (= 5.2.3)
actionview (= 5.2.3)
activejob (= 5.2.3)
activemodel (= 5.2.3)
activerecord (= 5.2.3)
activestorage (= 5.2.3)
activesupport (= 5.2.3)
bundler (>= 1.3.0)
railties (= 5.2.3)
sprockets-rails (>= 2.0.0)
rails-controller-testing (1.0.4)
actionpack (>= 5.0.1.x)
actionview (>= 5.0.1.x)
activesupport (>= 5.0.1.x)
rails-dom-testing (2.0.3)
activesupport (>= 4.2.0)
nokogiri (>= 1.6)
rails-html-sanitizer (1.0.4)
loofah (~> 2.2, >= 2.2.2)
railties (5.2.3)
actionpack (= 5.2.3)
activesupport (= 5.2.3)
method_source
rake (>= 0.8.7)
thor (>= 0.19.0, < 2.0)
rake (12.3.2)
ransack (2.1.1)
actionpack (>= 5.0)
activerecord (>= 5.0)
activesupport (>= 5.0)
i18n
rb-fsevent (0.10.3)
rb-inotify (0.10.0)
ffi (~> 1.0)
redcarpet (3.4.0)
responders (2.4.1)
actionpack (>= 4.2.0, < 6.0)
railties (>= 4.2.0, < 6.0)
rspec-core (3.8.1)
rspec-support (~> 3.8.0)
rspec-expectations (3.8.4)
diff-lcs (>= 1.2.0, < 2.0)
rspec-support (~> 3.8.0)
rspec-mocks (3.8.1)
diff-lcs (>= 1.2.0, < 2.0)
rspec-support (~> 3.8.0)
rspec-rails (3.8.2)
actionpack (>= 3.0)
activesupport (>= 3.0)
railties (>= 3.0)
rspec-core (~> 3.8.0)
rspec-expectations (~> 3.8.0)
rspec-mocks (~> 3.8.0)
rspec-support (~> 3.8.0)
rspec-support (3.8.2)
ruby_dep (1.5.0)
sass (3.7.3)
sass-listen (~> 4.0.0)
sass-listen (4.0.0)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
sass-rails (5.0.7)
railties (>= 4.0.0, < 6)
sass (~> 3.1)
sprockets (>= 2.8, < 4.0)
sprockets-rails (>= 2.0, < 4.0)
tilt (>= 1.1, < 3)
sentry-raven (2.9.0)
faraday (>= 0.7.6, < 1.0)
shoulda-matchers (4.0.0.rc1)
activesupport (>= 4.2.0)
simplecov (0.16.1)
docile (~> 1.1)
json (>= 1.8, < 3)
simplecov-html (~> 0.10.0)
simplecov-html (0.10.2)
sprockets (3.7.2)
concurrent-ruby (~> 1.0)
rack (> 1, < 3)
sprockets-rails (3.2.1)
actionpack (>= 4.0)
activesupport (>= 4.0)
sprockets (>= 3.0.0)
thor (0.20.3)
thread_safe (0.3.6)
tilt (2.0.9)
tzinfo (1.2.5)
thread_safe (~> 0.1)
websocket-driver (0.7.0)
websocket-extensions (>= 0.1.0)
websocket-extensions (0.1.3)
PLATFORMS
ruby
DEPENDENCIES
active_material
activeadmin
aws-sdk-s3
bootsnap (>= 1.1.0)
byebug
clearance
factory_bot_rails
faker
fast_jsonapi
health_check
listen (>= 3.0.5, < 3.2)
mini_magick
pg
puma (~> 3.11)
quandl-config
rails (~> 5.2.1, != 5.2.1.1)
rails-controller-testing
redcarpet
rspec-rails
sass-rails
sentry-raven
shoulda-matchers (= 4.0.0.rc1)
simplecov
RUBY VERSION
ruby 2.5.1p57
BUNDLED WITH
2.0.2
The problem happens because one of the gem activeadmin v 1.4.3
was requiring coffee-script v4.2.2
but the new activeadmin v2.3.1
does not require this gem anymore and bummr
is still trying to update it.
I'm not sure if this is due to some changes on the Bundler side, but lately, Bummr hasn't been able to detect updates, even with the --all
option. Here is a run from just now in this repo: https://github.com/codeforamerica/ohana-web-search
Bummr 0.5.0
To run Bummr, you must:
- Be in the root path of a clean git branch off of master
- Have no commits or local changes
- Have a 'log' directory, where we can place logs
- Have your build configured to fail fast (recommended)
- Have locked any Gem version that you don't wish to update in your Gemfile
- It is recommended that you lock your versions of `ruby` and `rails` in your `Gemfile`
Your test command is: 'bundle exec rake'
Bummr will run with the following options:
--all: false
Run `bummr help update` for more information.
Are you ready to use Bummr? (y/n) y
Ready to run bummr.
Bummr update initiated 2021-04-09 22:28:06 -0400
Fetching gem metadata from https://rubygems.org/..........
Resolving dependencies...............
Gem Current Latest Requested Groups
addressable 2.5.2 2.7.0
ast 2.4.1 2.4.2
benchmark-ips 2.8.2 2.8.4
capybara 3.34.0 3.35.3 >= 0 test
chunky_png 1.3.11 1.4.0
crack 0.4.4 0.4.5
derailed_benchmarks 1.7.0 2.0.1
diff-lcs 1.3 1.4.4
docile 1.3.2 1.3.5
faraday 0.17.3 1.3.0
ffi 1.14.2 1.15.0
font-awesome-rails 4.7.0.5 4.7.0.7 >= 0 default
get_process_mem 0.2.5 0.2.7
google-api-client 0.52.0 0.53.0 ~> 0.9 default
googleauth 0.14.0 0.16.1
haml_lint 0.36.0 0.37.0 >= 0 test
heapy 0.1.4 0.2.0
i18n 1.8.9 1.8.10
json 2.3.0 2.5.1
launchy 2.4.3 2.5.0
listen 3.1.5 3.5.1
loofah 2.9.0 2.9.1
memory_profiler 0.9.14 1.0.0
mini_histogram 0.1.3 0.3.1
mini_mime 1.0.3 1.1.0
nio4r 2.5.4 2.5.7
nokogiri 1.11.2 1.11.3
nokogiri 1.11.2 1.11.3
parser 2.7.2.0 3.0.1.0
psych 3.2.1 3.3.1
public_suffix 3.1.1 4.0.6
puma 5.1.1 5.2.2 >= 0 default
rack-mini-profiler 2.2.0 2.3.1 >= 0 development
rb-fsevent 0.10.3 0.10.4
reek 6.0.2 6.0.3 >= 0 development
regexp_parser 1.8.2 2.1.1
rexml 3.2.4 3.2.5
rspec-core 3.9.1 3.9.3
rspec-expectations 3.9.1 3.9.4
rspec-support 3.9.2 3.9.4
rubocop 1.6.1 1.12.1 >= 0 test
rubocop-ast 1.3.0 1.4.1
ruby-progressbar 1.10.1 1.11.0
ruby-statistics 2.1.2 2.1.3
ruby_parser 3.13.1 3.15.1
sawyer 0.8.1 0.8.2
semantic_range 2.3.1 3.0.0
sexp_processor 4.12.1 4.15.2
signet 0.14.0 0.15.0
sprockets-rails 3.2.1 3.2.2
unicode-display_width 1.7.0 2.0.0
webdrivers 4.4.1 4.6.0 >= 4.1.2 test
webmock 3.11.0 3.12.2 >= 0 test
yard 0.9.25 0.9.26 >= 0 development
No outdated gems to update
Unless I'm misremembering, I'm pretty sure that when a gem that was specified in the Gemfile was outdated, bummr used to be able to detect that. For example, I would expect it to upgrade google-api-client
, which is specified like this in the Gemfile:
gem 'google-api-client', '~> 0.9'
Hi @lpender, I started looking into license compliance for some projects I'm working on, and we can't use a gem that uses the GPL license without our project changing its license to GPL, which we don't want to do. The colorize
gem uses the GPL-2 license, and the owner of the project doesn't seem to want to change it. See this issue: fazibear/colorize#47
In that thread, someone recommended the rainbow gem, which seems like a good alternative. Would you consider switching to rainbow?
I noticed that you use the MIT license for bummr
, but because you use colorize
, you would need to convert to a GPL-2 license, which is probably not what you want.
I'm using bummr on Rails 4.1 and I'm getting this warning all the time;
[WARNING] Attempted to create command "check" without usage or description. Call desc if you want this method to be available as command
or declare it inside a no_commands{} block. Invoked from "/usr/local/rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/bummr-0.2.1/lib/bumm
r/check.rb:5:in `<class:Check>'".
Starting a 4.2 -> 5.0 -> 5.1 -> 5.2 upgrade sequence, I was looking at bummr as a way to get the current non-rails gems updated prior to the jump to the next version.
Does/can bummr exclude Rails itself from the upgrade process, to support a .X at a time upgrade workflow?
For example, I had Rails 4.2.5.1, but it did not get updated to 4.2.6:
rails not updated from 4.2.5.1, requested ~> 4.2.0 to latest: 4.2.6
If you have a version constraint in the Gemfile, such as gem 'devise', '~> 3.4'
, and if there is a new version available that is within the constraints, the commit message includes extra text that refers to the constraint, such as:
Update devise from 3.5.6, requested ~> 3.4 to 3.5.10
Hello. I'm not sure what is causing this, but every time I run bummr update
, it fails to create the separate commits for each gem update, and displays the following error:
fatal: pathspec 'vendor/cache' did not match any files
Commit: Update yard from 0.9.16 to 0.9.18
On branch mb-bummr
Changes not staged for commit:
modified: Gemfile.lock
no changes added to commit
error: cannot rebase: You have unstaged changes.
error: Please commit or stash them.
Ready to run bummr.
Do you want to test the build now?
I tried on 2 different repos, and with bummr versions 0.3.2, 0.4.0, and the master branch. Any idea what might be going on?
I have Git version 2.20.1 installed via Homebrew.
That last time I ran bummr successfully was on November 11 with version 0.3.2. It sounds like perhaps something on my machine is causing this, possibly the Git version?
I'm not sure if I'm using this correctly but after it ran for a long time doing it's update with 'bummr update' it stopped as it found some untracked files in my branch (because I cache the gems in vendor/cache). So I had to start 'bummr test' manually. I thought this would run tests and bisect bad/good depending if they passed and go to the next commit, is this correct?
The problem I'm having is when I run bummr test it runs my tests and 4 fail out of 906 and then it displays the following and stops on the terminal
Ready to run bummr.
Bad commits found! Bisecting...
You need to give me at least one good and one bad revisions.
(You can use "git bisect bad" and "git bisect good" for that.)
Then I have to manually 'git bisect bad', now do I run bummr test again here or is this something bummr should be doing automatically?
For my project I keep a vendor/cache directory just incase rubygems goes down and bummr doesn't play nicely with this directory as it doesn't add it to git when committing. I propose that the following line be changed to include the vendor/cache directory when committing changes.
Thanks for merging #41 so quickly & cutting the 0.1.8
release. I noticed on the bummr
versions listed on Rubygems that 0.2.0
was released (accidentally?) in March?
Currently when one runs gem install bummr
you get:
Fetching: bummr-0.2.0.gem (100%)
Successfully installed bummr-0.2.0
1 gem installed
Which isn't actually the latest code. It might be worth yanking 0.2.0
- or skipping ahead 0.3.0
?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.