feat(cli): Attempt at patching the existing event with a new file reader to support trunk based flows #63
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
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.
For trunk based builds, the Slack notifications are broken like this example:
https://monta-app01.slack.com/archives/C01KL9FUPNK/p1713440134273099
Trunk based flows use another pattern for their github json events. The original class GithubPushContext, is coupled with the
PublishSlackServiceandPublishSlackCommand, so to avoid re-writing these i created a quick util method which populates the original context with the new info.Theres prob also a way of doing this in a OOP style which would be cleaner and better but for now i think this is alright.