feat: Support appending to message attachments instead of replacing #74
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 php release flow, we would like timestamps on the events, e.g. when build started, when deploy finished. To support that, I've added a flag called
append-status-updates
which will add new attachments with status updates incl timestamp to existing slack messages instead of replacing them with new status.I've added two tests; one of the replacing functionality and one of the appending functionality
To make the tests work, I had to inject a layer between the message builder and the http client in
SlackClient
, which I callSlackHttpClient
, which I then replace with a fake instance during testing, to assert on the messages and content that would be sent to slack.Disclaimer: This is my first Kotlin PR ever, so I accept a lot of feedback. :D