Revert "Don’t send emails for HMCTS content items" #149
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 5dff395. Blocking emails for HMCTS content was temporary, while we bulk-published some imported forms. All the content has been published, so the block should be removed. https://trello.com/c/pEencybh/89-hmcts-step-3b-spike-suppression-of-emails-being-sent-on-publish
rubenarakelyan
approved these changes
Mar 20, 2018
suzannehamilton
changed the title
|
The department's given us the OK, so I'll merge this now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This reverts commit 5dff395.
Blocking emails for HMCTS content was temporary, while we bulk-published some imported forms. All the content has been published, so the block should be removed.
https://trello.com/c/pEencybh/89-hmcts-step-3b-spike-suppression-of-emails-being-sent-on-publish
Marked as "do not merge" because we shouldn't deploy this until the 21st of March.
cc @rubenarakelyan