Run complete C++ SDK packaging step whenever a push to "dev" occurs. #184
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
This reverts commit 16e7b5c.
… as it uses later.
….com/firebase/firebase-cpp-sdk into feature/run_packaging_on_push_to_dev
DellaBitta
approved these changes
Nov 12, 2020
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.
Whenever a feature branch is merged into "dev", this will kick off a full C++ packaging workflow on that push. (All of the inputs are blank strings in this case, so ensure that blank inputs are treated as default.)
This ensures that we always have an up-to-date package for the latest 'dev' branch, and is an alternative to setting up a cron workflow (as cron will only work once we move back to the 'master' branch).