Migrate local Ruby podspecs to JSON #3147
Merged
+13
−1
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
|
👍 |
|
This can be merged once rebased. |
|
I don't believe we have any tests for migrations -Samuel E. Giddins On Feb 16, 2015, at 6:21 AM, Kyle Fuller notifications@github.com wrote: Tests && rebase? — |
segiddins
force-pushed
the
seg-podspec-migrator
branch
2 times, most recently
from
0699b3f
to
5adc6fc
Compare
…se pods to work What 1eb3584 should have been
segiddins
force-pushed
the
seg-podspec-migrator
branch
from
5adc6fc
to
3e82d50
Compare
segiddins
added a commit
that referenced
this pull request
Feb 17, 2015
Migrate local Ruby podspecs to JSON
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.
Closes #3038.
\c @neonichu @kylef