From 3e18e25f43f416ee7a88c716a428457b914cf3fc Mon Sep 17 00:00:00 2001
From: Rohan Adwankar <39285979+RohanAdwankar@users.noreply.github.com>
Date: Mon, 2 Nov 2026 11:48:23 -0800
Subject: [PATCH] docs: require one component per pull request

Require separate pull requests for distinct features and separable components, keep related tests and docs together, and document dependencies between PRs.

Signed-off-by: Rohan Adwankar <39285979+RohanAdwankar@users.noreply.github.com>
---
 CONTRIBUTING.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a777fac..daedce4 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -14,6 +14,12 @@ Open an issue before substantial implementation work so maintainers can confirm
 
 ## Code Contributions
 
+### Pull request scope
+
+Each pull request must contain one independently reviewable component: a single feature, bug fix, refactor, or documentation change. Split work involving multiple features or separable components into individual pull requests, even when they support the same larger goal. Separate commits within one pull request do not replace separate pull requests.
+
+Keep the implementation, tests, and documentation needed for that component together. If a component depends on another pull request, link the dependency and describe the review and merge order. Maintainers will ask for bundled changes to be split before review.
+
 1. Fork the repository and create a focused branch from `main`.
 2. Keep changes minimal and include documentation for user-visible behavior.
 3. Validate the Helm chart: