Commit 4f735758bd for openssl.org

commit 4f735758bdb3e6d5f33b6fbf4d60bbb4ea896907
Author: Pauli <paul.dale@oracle.com>
Date:   Thu Feb 19 11:29:23 2026 +1100

    Update documentation with guidelines for commit and PR messages

    The CONTRIBUTING.md and PULL_REQUEST_TEMPLATE.md files have been updated
    to include guidelines on what makes a desirable commit message and
    PR description.

    Reviewed-by: Matt Caswell <matt@openssl.org>
    Reviewed-by: Nikola Pajkovsky <nikolap@openssl.org>
    Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com>
    (Merged from https://github.com/openssl/openssl/pull/30075)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 85cfb3741c..d4a80e7e47 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -3,7 +3,9 @@ Thank you for your pull request. Please review these requirements:

 Contributors guide: https://github.com/openssl/openssl/blob/master/CONTRIBUTING.md

-Other than that, provide a description above this comment if there isn't one already
+Include a clear description of the issue or feature above this comment if not already provided. This should briefly outline the issue or feature being addressed, along with any relevant implementation details. For performance improvements, include benchmark results as well.
+
+Pull requests and commits should be self-contained, allowing readers to understand what changed and why without needing to reference related issues or having prior knowledge. Individual commit messages should include all relevant details to ensure future contributors can easily follow the git history. Clearly explain what is changing and why, and feel free to include detailed (long) descriptions when beneficial to understanding.

 If this fixes a GitHub issue, make sure to have a line saying 'Fixes #XXXX' (without quotes) in the commit message.
 -->
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5b28d8776a..388f9a8e13 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -27,6 +27,15 @@ communication before submitting many pull requests. In addition,
 contributors should personally evaluate potential patches generated by
 automated tools.

+Provide a clear description of the issue or feature being addressed,
+including any relevant implementation details and, for performance
+improvements, benchmark results. Pull requests and commits should be
+self-contained, enabling readers to understand what changed and why
+without needing to reference related issues or having prior knowledge. Commit
+messages should include all relevant details to help future contributors
+follow the git history, with clear explanations of what is changing
+and why. Long descriptions are encouraged if they aid understanding.
+
 To make it easier to review and accept your pull request, please follow these
 guidelines: