Repository navigation
Fill gaps from assistant conversations: email alerts and variable escaping - #591
Merged
Merged
Conversation
…ters in variables
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
…caping Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Button labels match the app (+ Add more channels / New alert channel, Create email), the permission note names the roles instead of a permission that doesn't exist, and double-bracket variables are described as HTML-escaped, not URI encoded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was successfully deployed
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
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.
Summary
Addresses recurring assistant questions about adding an email address to a monitor's alerts and special characters being escaped in API check variables.
Changes
&to avoid&.Context
Based on unanswered assistant threads from the past week. Coralogix inbound-metrics question reflects a feature request, not a docs gap, so it was left out.