Repository navigation
gh-1359: Document follow-up for out-of-scope review suggestions - #1940
badrisatyam1-ctrl wants to merge 2 commits into
Conversation
|
All commit authors signed the Contributor License Agreement. |
Documentation build overview
|
|
Please sign the CLA, we cannot review otherwise. |
|
@badrisatyam1-ctrl It would be helpful if you can limit the number of open PRs to something like three. Opening a lot in a short amount of time makes it difficult for us to review. You can keep these open, but please don't open more. Also, please don't needlessly update your branch from Finally, make sure you read the AI policy. It's important you have read and understand the changes in your PRs, and that you've not just let your LLM create them on autopilot. I don't want to be the first human to read "your" text. It definitely looks like you've not read this PR, because the description contains "\n" chars: 
|
Closes #1359\n\nAdd concise guidance for tracking a concrete review suggestion that is outside the current PR scope: agree who will track it, then create an issue or PR linking to the original comment. Clarify that opening an issue is a reminder and context, not a commitment to implement the follow-up.\n\nValidation: git diff --check passed. No tests were run for this documentation-only change.\n\nAI disclosure: OpenAI Codex assisted with research and drafting; the text was checked against the issue discussion and current guide.