Repository navigation
docs: bring pending doc updates onto main - #1070
Merged
Merged
Conversation
… console entry points
…ise analysis and calendar updates
…solve modes and auto-analysis
This was referenced Oct 17, 2026
Closed
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.
Brings the still-relevant content of several open docs PRs onto current
main. Each of those PRs conflicted withmain, so the content was re-applied hunk by hunk against the current pages instead of rebasing. Every added fact was checked against the product source on its default branch. Claims that could not be confirmed were left out.--fields, theFLASHDUTY_CONSOLE_URLreserved variable, MCP/Skill list entry points, AI SRE as a work-item assignee, RUM Issue auto-analysis, dashboard panel refresh, and IM attachments plus the topic-session lookback. Left out: refresh queue-jumping and the DingTalk reaction table (not confirmable).run_in,chat_scope_mismatch), RUM resolve modes, DingTalk/Feishu member auto-linking and Slack linking, literal wildcards in filters and routing rules, CLImonit folder-*/--run-in, and Go SDKRuleFolders/Automations. Left out: the stored-value rewrite note and the concurrent-run skip claim.device_type:Mobileexample fix. The Ask AI rewrite does not match the shipped RUM explorer, which still uses the preview-and-apply flow.resolve_modeand the automation execution-location fields are already onmainwith more accurate wording.incident_idfilter is not in the released API, andrefis already documented.Also adds changelog entries for 10-12, 10-15 and 10-16.
Checks:
mint broken-linksandmint validatepass,scripts/api_path_redirects.py --checkandscripts/lint_openapi.pypass, and the integration-docs build/check passes (348 keys).