feat: playbook as notification recipient #1679
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
adityathebe
force-pushed
the
feat/playbook-as-notification-recipient
branch
4 times, most recently
from
2e8d61c to
65296a9
Compare
moshloop
reviewed
Dec 19, 2024
adityathebe
force-pushed
the
feat/playbook-as-notification-recipient
branch
5 times, most recently
from
41623f9 to
46a4e45
Compare
|
@adityathebe can you add a test ? |
adityathebe
force-pushed
the
feat/playbook-as-notification-recipient
branch
from
46a4e45 to
0cacd99
Compare
adityathebe
force-pushed
the
feat/playbook-as-notification-recipient
branch
from
0cacd99 to
110dde3
Compare
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.
resolves: #1420