Repository navigation
chore: format runtime configuration table [skip ci] - #173
Merged
osipovartem merged 1 commit intoNov 1, 2026
Merged
osipovartem merged 1 commit into
osipovartem merged 1 commit into
Conversation
github-actions
Bot
added
the
documentation
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.
Which issue does this PR close?
No separate issue. This repairs the generated configuration-table formatting in the pinned runtime branch.
Rationale for this change
The standard local lint suite rejects
docs/source/user-guide/configs.mdwith its pinned Prettier 2.7.1. A prior configuration update left the table padding and separator widths out of sync.What changes are included in this PR?
Format that table only. No configuration values, descriptions, links, or code blocks change.
Are these changes tested?
dev/rust_lint.shsuite passes, including Markdown formatting and strict rustdoc.Are there any user-facing changes?
None.