Right now I'm using Callisto in a workflow where the Pull Request is created when the task is finished. Therefore our approach with posting the build result to GitHub won't really work. Adding Slack support as it will be an improvement for such use cases.
Tasks
[x] Refactor duplicated code
[x] Add PostSlackAction class
[x] Implement -ignore parameter in PostSlackAction (When filtering in the summarize step we lose the keywords for slack)
Infos for reviewer
The formatting of slack messages did change a bit. Now errors, warnings & unit tests are grouped together (and use the corresponding color). Unfortunately it uses the outdated format. Not sure if I have time to support the new Blocks API https://api.slack.com/tools/block-kit-builder
Description
Right now I'm using Callisto in a workflow where the Pull Request is created when the task is finished. Therefore our approach with posting the build result to GitHub won't really work. Adding Slack support as it will be an improvement for such use cases.
Tasks
PostSlackActionclassPostSlackAction(When filtering in the summarize step we lose the keywords for slack)Infos for reviewer
The formatting of slack messages did change a bit. Now errors, warnings & unit tests are grouped together (and use the corresponding color). Unfortunately it uses the outdated format. Not sure if I have time to support the new Blocks API https://api.slack.com/tools/block-kit-builder
Preview
Note should be merged after #8