feat(gh): add workflow to trigger grpc client update #1198
Merged
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## main #1198 +/- ##
=======================================
Coverage 79.87% 79.87%
=======================================
Files 38 38
Lines 2758 2758
=======================================
Hits 2203 2203
Misses 451 451
Partials 104 104 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
This worked so updating the description.
This adds an action which is currently configured to fire on
workflow_dispatch.When triggered, it authenticates to flipt-io/flipt-grpc-go and triggers the proto update workflow.
I will update this so that it will be triggered on
releaseevents. So that we can propagate updates to clients.