Summary

What happens?

Use Cases

When would you use this?

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Current behavior

Slack, email and other notifications provide a standardized text and backend info.

Proposed behavior

Users can add custom texts to the notifications.

Example

Prefect
Failed
awesome-flow is now in a Failed state
Message
Some reference tasks failed.
Prefect notification
@colleague, please analyze possible root causes.

Ideas for Imp

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.

Issue

16 files has some sort of Sugar Pro references in code as comments.
Those should be removed

Steps to Reproduce

Try the search with BEGIN: pro
https://github.com/salesagility/SuiteCRM/search?q

In order to get a graph for history of this schedule I have to know to click on "slack_digest_pipeline" and then the Partitions tab.

Only then do I get the hotness:

![Screen Shot 2020-10-02 at 10 40 19 AM](https://user-images.githubusercontent.com/

Had the branch ancestry:

branch-1
  branch-2-bug-fix
    branch-3

All three branches had an open PR. branch-2-bug-fix‘s PR was a duplicate of a fix that someone else had already put in and merged at the same time. I closed the PR on branch-2-bug-fix and ran git town kill on that branch.

I was expecting it to change the base branch of branch-3‘s PR but instead it closed it