CircleCI: Publish pods when the repo is tagged #1219
Merged
Conversation
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
jtreanor
force-pushed
the
circleci-publish
branch
from
7e854a7 to
73d74f1
Compare
jkmassel
approved these changes
Oct 5, 2019
Contributor
jkmassel
left a comment
jkmassel
left a comment
There was a problem hiding this comment.
I see that both podspec files are covered here, so this looks good to me!
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.
Description
Adding a CircleCI job that will run
pod trunk pushon the podspec whenever the repo is tagged. This is already in use and tested on WordPressAuthenticator.Testing Details
We can't really test this directly on the PR, but you can see it was tested here: wordpress-mobile/circleci-orbs#38