chore: API documentation sync - #621
Conversation
Greptile SummaryThis automated documentation sync adds REVIEW as an agent run mode and documents the new optional
Confidence Score: 4/5The documentation should be corrected before merging because the new The newly documented field points to a nonexistent in-page type definition, preventing API consumers from discovering its accepted values. Files Needing Attention: pages/api-reference/kubernetes/agent-api-reference.md
|
| Filename | Overview |
|---|---|
| pages/api-reference/kubernetes/agent-api-reference.md | Adds REVIEW mode and reviewDepth, but the new type link points to a definition that is absent from the page. |
Reviews (1): Last reviewed commit: "sync docs" | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| | `branch` _string_ | Branch is the repository branch the agent should operate on. If omitted, the repository default branch is used. | | Optional: \{\} <br /> | | ||
| | `mode` _[AgentRunMode](#agentrunmode)_ | Mode defines how the agent should run (ANALYZE, WRITE) | | Required: \{\} <br /> | | ||
| | `mode` _[AgentRunMode](#agentrunmode)_ | Mode defines how the agent should run (ANALYZE, WRITE, REVIEW) | | Required: \{\} <br /> | | ||
| | `reviewDepth` _[AgentReviewDepth](#agentreviewdepth)_ | ReviewDepth controls how far a review run explores code adjacent to the pull request changes. | | Optional: \{\} <br /> | |
There was a problem hiding this comment.
When a reader follows the new AgentReviewDepth link to determine the accepted reviewDepth values, it targets an absent #agentreviewdepth definition, leaving the field's valid values undocumented.
Knowledge Base Used: API reference rendering
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
1 participant
Automated pull request to sync docs for: