Allow Continue on Failure on Teams Notifications #4098
Merged
+54
−12
Conversation
This file contains hidden or 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
Since a Teams notification is not necessarily an essential part of a deploy, we should allow users to continue the deploy should a notification fail to send.
jaxdestroyer
approved these changes
Jul 14, 2025
antonmedv
approved these changes
Jul 14, 2025
Contributor
Author
|
@antonmedv I appreciate you adding this to v8.0.0-alpha.3, but is there any way this could get tagged in a v7 release so I can utilize it in an active project? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Since a Teams notification is not necessarily an essential part of a deploy, we should allow users to continue the deploy should a notification fail to send.
[No] Bug fix #…?
[Yes] New feature?
[No] BC breaks?
[Yes ] Tests added?
[Yes] Docs added?