You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
When using a :gitsource for a gem, the output when running bundle install does not include the commit hash, simply the branch:
Output
Fetching git@github.com:revett/composition.git
Using composition 0.0.1 from git@github.com:revett/composition.git (at master)
This makes it look as though it's using the latest version of the gem from master. However the Gemfile.lock locks the gem to any previous commit hash (whenever the gem was last updated).
Would be great to have this information in the output - very helpful in the console output of Jenkins CI jobs for example.
Gemfile
source "https://rubygems.org/"
group :production do
gem "composition", :git => "git@github.com:revett/composition.git"
gem "faraday"
gem "mustache", "~> 0.99.5"
end
The text was updated successfully, but these errors were encountered:
This effectively changes the output of commands that use Source::Git#to_s
(ie. `bundle install`). For example:
Using rack 1.0.0 from git@github.com:rack/rack.git (at master@574b147)
Closes#3433.
This effectively changes the output of commands that use Source::Git#to_s
(ie. `bundle install`). For example:
Using rack 1.0.0 from git@github.com:rack/rack.git (at master@574b147)
Closes#3433.
This effectively changes the output of commands that use Source::Git#to_s
(ie. `bundle install`). For example:
Using rack 1.0.0 from git@github.com:rack/rack.git (at master@574b147)
Closes#3433.
When using a
:git
source for a gem, the output when runningbundle install
does not include the commit hash, simply the branch:This makes it look as though it's using the latest version of the gem from master. However the
Gemfile.lock
locks the gem to any previous commit hash (whenever the gem was last updated).Would be great to have this information in the output - very helpful in the console output of Jenkins CI jobs for example.
The text was updated successfully, but these errors were encountered: