From 897c79084f79ffcf95524b1e9f3b56d34896da22 Mon Sep 17 00:00:00 2001 From: Matteo Golin Date: Fri, 5 Sep 2025 11:42:34 -0400 Subject: [PATCH] docs/codeowners: Provide some relevant information about CODEOWNERS. Some brief information in the contributing workflow to tell new contributors about the CODEOWNERS file and what it achieves. Signed-off-by: Matteo Golin --- Documentation/contributing/making-changes.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/Documentation/contributing/making-changes.rst b/Documentation/contributing/making-changes.rst index 0d035fb819..a60182210b 100644 --- a/Documentation/contributing/making-changes.rst +++ b/Documentation/contributing/making-changes.rst @@ -265,6 +265,21 @@ squash before submitting the Pull Request: happy, they may suggest squashing and merging again to make a single commit. In this case you would repeat steps 1 through 6. + .. note:: + + NuttX uses a ``CODEOWNERS`` file to help track which users are "experts" + on certain NuttX subsystems. Sometimes, this will result in certain + reviewers being automatically requested to review your PR if you have + modified a file they are marked as a "code owner" for. This is just to + help contributors get more relevant reviews from someone who knows the + subject area. + + If you've created a new file, let's say for a driver, you can add yourself + as a code owner for that file by modifying ``.github/CODEOWNERS``. Read + the `GitHub documentation for CODEOWNERS + `_ + for more information. + How to Include the Suggestions on Your Pull Request? ====================================================