docs: fix broken fragment anchors in EN reference pages#518
Open
jimpablo wants to merge 1 commit into
Open
Conversation
|
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates English reference docs to point to the correct section anchors for related configuration and interaction pages.
Changes:
- Updated internal doc links/anchors in tools, slash-commands, and keyboard references
- Replaced previously CN-anchor fragments with EN-anchor fragments
- (Unintentionally) introduced literal line numbers into Markdown content, which breaks formatting
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| docs/en/reference/tools.md | Updates env var anchor; currently injects a literal “115 |
| docs/en/reference/slash-commands.md | Updates provider management anchor; currently injects a literal “17 |
| docs/en/reference/keyboard.md | Updates interaction guide anchor; currently injects a literal “72 |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## Scheduled Tasks | ||
|
|
||
| Scheduled task tools allow the Agent to re-inject a prompt into the current session at a future time — either as a one-time reminder or as a recurring cron-triggered task (periodic checks, daily reports, deployment monitoring, etc.). Schedules are bound to the session and remain active after `kimi resume`, but are not carried into a brand-new session. A single session can hold at most 50 active scheduled tasks. Set `KIMI_DISABLE_CRON=1` to disable them entirely; see [Environment Variables](../configuration/env-vars.md#运行时开关). | ||
| Scheduled task tools allow the Agent to re-inject a prompt into the current session at a future time — either as a one-time reminder or as a recurring cron-triggered task (periodic checks, daily reports, deployment monitoring, etc.). Schedules are bound to the session and remain active after `kimi resume`, but are not carried into a brand-new session. A single session can hold at most 50 active scheduled tasks. Set `KIMI_DISABLE_CRON=1` to disable them entirely; see [Environment Variables](../configuration/env-vars.md#runtime-switches). |
| | `/login` | — | Select an account or platform and log in: Kimi Code uses OAuth device-code flow; Kimi Platform uses API key login | No | | ||
| | `/logout` | — | Clear credentials for the currently selected account | No | | ||
| | `/provider` | — | Open the interactive provider manager to view, add, and remove configured providers. See [Platforms & Models — `/provider` and provider management](../configuration/providers.md#provider-与供应商管理) | Yes | | ||
| | `/provider` | — | Open the interactive provider manager to view, add, and remove configured providers. See [Platforms & Models — `/provider` and provider management](../configuration/providers.md#provider-—-interactive-provider-management) | Yes | |
| | `/login` | — | Select an account or platform and log in: Kimi Code uses OAuth device-code flow; Kimi Platform uses API key login | No | | ||
| | `/logout` | — | Clear credentials for the currently selected account | No | | ||
| | `/provider` | — | Open the interactive provider manager to view, add, and remove configured providers. See [Platforms & Models — `/provider` and provider management](../configuration/providers.md#provider-与供应商管理) | Yes | | ||
| | `/provider` | — | Open the interactive provider manager to view, add, and remove configured providers. See [Platforms & Models — `/provider` and provider management](../configuration/providers.md#provider-—-interactive-provider-management) | Yes | |
| ## Approval Panel | ||
|
|
||
| When the Agent initiates a tool call that requires confirmation, the TUI displays an approval panel. For the full approval workflow, see [Interaction & Input](../guides/interaction.md#审批流程). The available keys inside the panel are: | ||
| When the Agent initiates a tool call that requires confirmation, the TUI displays an approval panel. For the full approval workflow, see [Interaction & Input](../guides/interaction.md#approval-flow). The available keys inside the panel are: |
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.
Problem
Three English reference pages link to Chinese-language fragment anchors that do not exist on the corresponding EN pages (VitePress generates anchors from the heading text, so the EN pages have English anchors). Clicking these links opens the correct page but fails to scroll to the target section.
en/reference/slash-commands.md#provider-与供应商管理#provider-—-interactive-provider-managementen/reference/tools.md#运行时开关#runtime-switchesen/reference/keyboard.md#审批流程#approval-flowThe Chinese anchors were likely carried over from the ZH docs during the EN translation (#386 / #391) and were not updated to match the English headings.
The corresponding ZH docs are correct — they use the same Chinese anchors and the ZH pages have Chinese headings, so the anchors match.
What changed
Replaced the three Chinese fragment anchors with the correct English anchors generated by VitePress from the EN heading text. 3 files, 3 lines changed.
Verification
pnpm -C docs run build— passes with no broken-link warningsid="provider-—-interactive-provider-management",id="runtime-switches",id="approval-flow")moonshotai.github.io/kimi-code) that the Chinese anchors returngetElementById → nullwhile the English anchors resolve correctlyChecklist
gen-changesetsskill, or this PR needs no changeset. (Docs-only, no changeset needed.)gen-docsskill, or this PR needs no doc update. (This is the doc fix.)