summaryrefslogtreecommitdiff
path: root/test/ruby/test_string.rb
diff options
context:
space:
mode:
authorEdouard CHIN <chin.edouard@gmail.com>2025-12-15 15:56:41 +0100
committergit <svn-admin@ruby-lang.org>2025-12-16 00:15:57 +0000
commitf88e7970901d3d8cfb6efeb536d983bf2e05b04a (patch)
tree1a180cf0b780f83b6d9ad61950f5d9d9d32d4177 /test/ruby/test_string.rb
parent98cac1a75d9d9b7ff4cfd5b5d0fd99c1b5f17631 (diff)
[ruby/rubygems] Allow bundle pristine to work for git gems in the same repo:
- Fix https://github.com/ruby/rubygems/pull/9186 - ### Problem Running `bundle pristine` in a Gemfile where there is many git gem pointing to the same repository will result in a error "Another git process seems to be running in this repository". ### Context This error is a regression since https://github.com/ruby/rubygems/commit/a555fd6ccd17 where `bundle pristine` now runs in parallel which could lead to running simultaneous git operations in the same repository. ### Solution When Bundler pristine a git gem it does a `git reset --hard` without specifying a path. This means the whole repository will be reset. In this case, we can leverage that by just pristining one gem per unique git sources. This is also more efficient. https://github.com/ruby/rubygems/commit/710ba514a8
Diffstat (limited to 'test/ruby/test_string.rb')
0 files changed, 0 insertions, 0 deletions