Add ci step to deploy firebase functions #2909
Open
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
sdowell
force-pushed
the
kpt-dev-vanity-server
branch
from
9de71e3 to
4c8bb59
Compare
|
@mengqiy Can you pl. take a look at this one ? |
sdowell
force-pushed
the
kpt-dev-vanity-server
branch
from
4c8bb59 to
5d824bc
Compare
sdowell
force-pushed
the
kpt-dev-vanity-server
branch
from
5d824bc to
0a3421f
Compare
This change is intended to automatically deploy firebase functions in addition to the already deployed hosted content on merge.
sdowell
force-pushed
the
kpt-dev-vanity-server
branch
from
0a3421f to
9cea2ef
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The existing deployment step deploys the static hosted content on merge. This change is intended to additionally add a step which deploys the recently added firebase functions upon merge.