Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance Slack webhook message readability #458

Open
TeemuSuoranta opened this issue Nov 23, 2020 · 2 comments
Open

Enhance Slack webhook message readability #458

TeemuSuoranta opened this issue Nov 23, 2020 · 2 comments

Comments

@TeemuSuoranta
Copy link
Contributor

seravo-webhook

Is your feature request related to a problem? Please describe.
You can include a Slack webhook URL that is pinged when updates fail. This is a much appreciated feature but at the moment reading these notification can be difficult to read as there is no repeating format and the site name is not emphasised.

Describe the solution you'd like
Create a format for these messages that makes it easy to look through these messages that might be pointed to a single Slack channel.

For example:

**{Site name}** {Site URL}: Cannot proceed with updating as the live site has errors that need to be addressed first

Seravo https://seravo.fi: Cannot proceed with updating as the live site has errors that need to be addressed first

If it is possible to point to additional info, it could be also like:

**{Site name}** {Site URL}: Cannot proceed with updating as the live site has errors that need to be addressed first. See more info at {URL to admin page}

The actual sending logic is outside of this plugin and probably inside some server scripts so I couldn't make a PR for these changes.

@TeemuSuoranta
Copy link
Contributor Author

TeemuSuoranta commented Nov 24, 2020

As there are notifications for both successful and failed attempts, you could also prefix the messages by emojis like 🆘 / ✅ so that issues can be easier to spot from other messages.

@ottok
Copy link
Contributor

ottok commented Nov 24, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants