Use :gitub key, :tag key, and production group in Gemfile #764
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Nice, thank you! |
kytrinyx
added a commit
that referenced
this pull request
Sep 17, 2013
Use :gitub key, :tag key, and production group in Gemfile
This was referenced Jul 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Two Gemfile related commits. I've left them as two commits as I think they add different things.
The first adds github and tag keys. Tags are important if bundling against master as it can easily vary experience on different systems. I've left the rouge one without as I believe you're hoping master will be updated to fix #157.
The newrelic to production thing just stops newrelic slowing down development/test mode (it can be really annoying in my experience).