From d4a7c20e04024dced5e5d2d70e6b250cbd56f364 Mon Sep 17 00:00:00 2001
From: Beqa <91750923+BeqaKs@users.noreply.github.com>
Date: Tue, 10 Nov 2026 06:13:39 +0400
Subject: [PATCH] docs: clarify coordination for overlapping PR fixes (#8931)

Say how to point at an overlapping change and then rebase, narrow, or close it, without implying a review date.
---
 CONTRIBUTING.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ad02d86048..063b71c47e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -130,6 +130,19 @@ status checks alongside its existing checks. Deploy the workflow to each
 protected target branch before requiring it there. The workflow reads PR
 metadata using trusted default-branch code and writes only a commit status.
 
+When an open PR may overlap another open change or a recently landed fix, note
+the related PR, issue, or commit in the description or a comment as soon as the
+overlap is known. Prefer one clear pointer over repeated status updates.
+
+If an overlapping change merges while a PR awaits review, link that commit on
+the open PR and state what remains useful. Rebase or otherwise align with the
+current base when the remaining work is still wanted, narrow the PR to the
+uncovered portion, or close it when the change is fully superseded. Keep the
+description and validation current after that update. Maintainers may also note
+the expected disposition (rebase, narrow, or close) when they land or recognize
+an overlapping fix. Readiness still does not grant merge permission or a review
+date.
+
 Maintainers may return a PR to the author or close it when the problem is
 unsupported, validation is missing, or the owner cannot explain the change.
 Contributors are responsible for completing this work before requesting review.