> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/dinghyfile-updates-do-not-trigger-slack-notifications.md).

# Dinghyfile updates do not trigger Slack notifications

### Issue <a href="#issue" id="issue"></a>

Dinghy has been configured to send pipeline update results to a Slack channel, but while updating the `dinghyfile` successfully creates pipeline changes - no notifications are being sent to the Slack channel.

### Cause <a href="#cause" id="cause"></a>

Dinghy's Slack notifications do not send if Dinghy's notifications are not explicitly enabled. This was a result of some changes made to code once Github Notifications became an option for Dinghy. As a result, customers will need to ensure that Dinghy notifications are enabled before setting Slack notifications. Once enabled, customers will want to also consider if they want to explicitly turn off GitHub Notifications as by default, they will be enabled. For some customers, depending on the size of Dinghy's repository, it may be desirable to keep Github notifications turned off, as per [the possible High number of GitHub emails generated after every Dinghyfile update](https://support.armory.io/support?id=kb_article_view\&sysparm_article=KB0010558).