From 8c7a64a6c231dc4a7c1369e3016b808ef2de0c29 Mon Sep 17 00:00:00 2001 From: Ryan Kurtz Date: Tue, 8 Sep 2026 07:40:11 -0400 Subject: [PATCH] GP-0: Updating CONTRIBUTING.md --- CONTRIBUTING.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b602d8c3c7..d693f6a95c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -57,8 +57,10 @@ smooth process when submitting a patch: - Unless it addresses a critical security update, avoid pull requests that update jars or other 3rd party libraries. It is preferred that these changes are made internally by the team. If you have a need for an updated library, please submit an issue with your request instead of a pull request. -- Before submission, please squash your commits using a message that starts with the issue number - and a description of the changes. +- Before submission, please squash your commits down to a single commit that briefly describes the + changes. +- Please do not include the issue number that is being fixed in the pull request title field. + Instead, use "Fixes #xxx" somewhere in the pull request description text box. - Isolate multiple patches from each other. If you wish to make several independent patches, do so in separate, smaller pull requests that can be reviewed more easily. - Avoid submitting self-generated binary files as part of your pull request. Despite your best