Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

bundle install - include commit hash for git source #3433

Closed
revett opened this issue Feb 26, 2015 · 1 comment
Closed

bundle install - include commit hash for git source #3433

revett opened this issue Feb 26, 2015 · 1 comment

Comments

@revett
Copy link

revett commented Feb 26, 2015

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
@revett
Copy link
Author

revett commented Feb 26, 2015

Similiar to #178.

agis added a commit that referenced this issue Oct 22, 2015
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.
agis added a commit that referenced this issue Oct 22, 2015
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.
agis added a commit that referenced this issue Oct 25, 2015
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.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants