{{ message }}
Repository navigation
Conversation
This was referenced Oct 17, 2026
Contributor
This was referenced Oct 17, 2026
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.

Related to #3764 and #1240. Part 1 of the GitHub Alerts implementation split from #5765. Menu integration follows in #5771.
Summary
Add a default-off GitHub Alerts setting and the editor/export support it controls. With the setting enabled, top-level GitHub alert syntax renders as NOTE, TIP, IMPORTANT, WARNING or CAUTION; disabling it exposes ordinary editable blockquotes.
github-alertblock with body-only children and type metadata, sharing container behavior with blockquotes.[!TYPE]+ Enter inside a quote, inner-block-first Backspace, empty-draft exit, copying, cutting, HTML paste and source-mode round trips.GitHub Alerts uses the same Markdown reparse and view-refresh path as the existing parsing-related settings, with no setting-specific selection or history handling.
Validation
build:unpackpassed.Tests ran in an isolated worktree. Temporary configuration allowing access to shared local dependencies was used for Vitest and is not committed.
Review order
Review and merge this PR first. Part 2 targets this branch so its diff contains only menu integration; after this PR merges, retarget Part 2 to
develop.Requirements, manual test documents and screenshots remain outside the repository. Existing screenshot evidence and discussion are preserved in #5765.