config: fix heading hierarchy for sub-section levels in tidb-configuration-file.md (#23160)#23167
config: fix heading hierarchy for sub-section levels in tidb-configuration-file.md (#23160)#23167ti-chi-bot wants to merge 2 commits into
Conversation
Change sub-section headings from ## to ### to properly reflect the config key hierarchy: - ## log.file → ### log.file (child of ## log) - ## opentracing.sampler → ### opentracing.sampler - ## opentracing.reporter → ### opentracing.reporter - ## tikv-client.copr-cache → ### tikv-client.copr-cache
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Code Review
This pull request adjusts the markdown heading levels in tidb-configuration-file.md for several configuration sections, including log.file, opentracing.sampler, opentracing.reporter, and tikv-client.copr-cache, to establish a correct and consistent heading hierarchy. There are no review comments, and I have no additional feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
This is an automated cherry-pick of #23160
What is changed, added or deleted? (Required)
Fix heading hierarchy in tidb-configuration-file.md for sub-section levels that incorrectly used
##instead of###:## log.file→### log.file(child of## log)## opentracing.sampler→### opentracing.sampler(child of## opentracing)## opentracing.reporter→### opentracing.reporter(child of## opentracing)## tikv-client.copr-cache→### tikv-client.copr-cache(child of## tikv-client)These dotted config key names indicate they belong to parent sections, so they should be rendered as sub-headings.
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?