Pass default changelog renderers through to custom renders#1154
Merged
ecraig12345 merged 3 commits intomainfrom Feb 13, 2026
Merged
Pass default changelog renderers through to custom renders#1154ecraig12345 merged 3 commits intomainfrom
ecraig12345 merged 3 commits intomainfrom
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
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.
Sometimes it's convenient to be able to reuse the default renderer in a custom renderer.
Also add very basic escaping to prevent comments like
Add --config <file> option(missing backticks around the placeholder) from being treated as HTML and breaking markdown rendering. Full escaping/sanitizing is the responsibility of the final markdown renderer, same as for a manually authored markdown file; the goal here is just to prevent the most common issue if somebody forgot their comment would be interpreted as markdown.