Add pluggable notification_types #22110
Merged
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
48 tasks
agrare
force-pushed
the
pluggable_notification_types
branch
from
e6f9435 to
7c1df0a
Compare
Allow plugins to bring their own notification_types in `content/notification_types.yml`
agrare
force-pushed
the
pluggable_notification_types
branch
from
7c1df0a to
249e639
Compare
|
Checked commit agrare@249e639 with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint |
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.
Allow plugins to bring their own notification_types in
content/notification_types.ymlRelated: ManageIQ/manageiq-providers-autosde#179
#19440