renamed anything referencing notifier or notifications to extensions to clarify repo intent #7
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
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.
What is this change?
This change primes the repo to be moved to a more descriptive name.
Why make this change?
As I've introduced this repo to colleagues, there's a common reaction that what they'll find here is smtp, slack, and chat-based messaging based on Cloud Deploy events. That is a use case and an important one but really this repo aims to more generically work with events emitted by Cloud Deploy to do anything one might deem useful. In this way, product features could even be trial ballooned through the automation here.
Links
#6