This repository was archived by the owner on Aug 8, 2023. It is now read-only.
Include iOS README in binary pod - #1886
Merged
Merged
Conversation
Contributor
|
👍 https://guides.cocoapods.org/making/quality-indexes.html
|
Contributor
|
Great work — just noticed this ranking business recently myself. Good discussion on the mailing list at https://groups.google.com/forum/#!topic/cocoapods/Pvjsd57zKAk as well. |
incanus
added a commit
that referenced
this pull request
Aug 19, 2015
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR adds the iOS-specific README to the build folder that gets zipped up and distributed as a CocoaPods binary pod. Without this README, CocoaPods dings the MapboxGL pod big time in its quality metrics for lacking a README. We’ve been compiling this README to serve as the index page of the API documentation that gets generated, but a README also needs to set right alongside the library and resource bundle.
/cc @incanus @friedbunny