Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Git non-bare repositories should validate the remote cache #5

Closed
adrienthebo opened this issue Jan 25, 2013 · 1 comment
Closed

Git non-bare repositories should validate the remote cache #5

adrienthebo opened this issue Jan 25, 2013 · 1 comment
Labels
bug

Comments

@adrienthebo
Copy link
Contributor

If an instantiated repository is changed to a remote then the cache remote should be updated. Right now the cache remote is set once blindly and never rechecked. This should be improved.
@adrienthebo adrienthebo mentioned this issue Apr 7, 2013
Closed
adrienthebo added a commit that referenced this issue Apr 7, 2013
@adrienthebo
(r10k-#5) Ensure git remote cache is set correctly
9514452
@adrienthebo
Copy link
Contributor Author

Released in 0.0.10

patrobinson pushed a commit to patrobinson/r10k that referenced this issue Jun 27, 2016
@scotje
Merge pull request puppetlabs#5 from puppetlabs/forge-api
7a29a9b 
Rollup of changes made to support Forge API service.
sarameisburger pushed a commit to sarameisburger/r10k that referenced this issue Apr 12, 2019
@stahnma
Merge pull request puppetlabs#5 from shrug/3.8.x
c241120 
Use GEM_HOME instead of Gem.path

Note that the ENV['GEM_HOME'] fun doesn't work with Ruby 2.1.5. And the method that works with Ruby 2.1.5 doesn't work in Ruby 1.9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@adrienthebo