From 8a4e73d9b55f87e669edf9adb3d3256d9a9ffdae Mon Sep 17 00:00:00 2001 From: Badri Vishal Pandey Date: Tue, 27 Oct 2026 17:44:14 +0530 Subject: [PATCH] gh-1359: Document review follow-up tracking --- getting-started/pull-request-lifecycle.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/getting-started/pull-request-lifecycle.rst b/getting-started/pull-request-lifecycle.rst index 3b8e09ae1..7daa0e970 100644 --- a/getting-started/pull-request-lifecycle.rst +++ b/getting-started/pull-request-lifecycle.rst @@ -619,6 +619,13 @@ back to them for changes). It is then expected that you update your pull request to address these comments, and the review process will thus iterate until a satisfactory solution has emerged. +Sometimes a review identifies a concrete improvement that is outside the scope +of the current pull request. Discuss who will follow up on it. Once someone +agrees to take responsibility for tracking it, create an issue or pull request +that links to the original review comment. The follow-up issue provides context +and a reminder; creating it does not by itself commit its author to implement +the change. + .. _how-to-review-a-pull-request: How to review a pull request