docs: promote CocoaPods to the second install option#16
Merged
Conversation
Move CocoaPods above the SwiftPM/XcodeGen manifest options now that the pod is published to Trunk, since 'pod install' is the most common path for many integrators. SwiftPM and XcodeGen shift to options 3 and 4.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Now that
PolyMessaging 0.7.0is published to CocoaPods Trunk, move the CocoaPods option up to Option 2 in the README Install section — it's the most common integration path for many teams. SwiftPM and XcodeGen shift down to options 3 and 4.New order:
Notes
pod install…" line that the reorder would otherwise have left orphaned under the XcodeGen block; it now lives only with the CocoaPods option.