Merge pull request #9451

4221051 docs: clarify proper PR title format (Gingeropolous)
This commit is contained in:
luigi1111 2024-12-23 10:35:22 -05:00
commit d02957e28d
No known key found for this signature in database
GPG Key ID: F4ACA0183641E010

View File

@ -43,6 +43,15 @@ Commit messages should be sensible. That means a subject line that
describes the patch, with an optional longer body that gives details,
documentation, etc.
Please reference the current merged PR list for a general subject line
format of the current contributors. As of 2024 the subject line uses the
following format:
subdirectory under src where changes were made: description of change
For example (PR #9189):
cryptonote_core: early out on out of bounds scaling parameter
When submitting a pull request on GitHub, make sure your branch is
rebased. No merge commits nor stray commits from other people in
your submitted branch, please. You may be asked to rebase if there