docs: documentation notifications configuration example #1610
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
Subscription supposed to lowercase and no pipe is need at the end Signed-off-by: Vikas Pogu <[email protected]>
Vikaspogu
force-pushed
the
notificationsconfiguration-doc-fix
branch
from
3d1c6cc to
67dcf35
Compare
svghadi
approved these changes
Nov 28, 2024
svghadi
changed the title
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.
Subscription supposed to lowercase and no pipe is need at the end
What type of PR is this?
What does this PR do / why we need it:
Notification configuration examples for subscriptions use uppercase letter and do not need to include a "|" at the end, which causes issues.
Have you updated the necessary documentation?
Which issue(s) this PR fixes:
Fixes #?
How to test changes / Special notes to the reviewer: