mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-09 05:29:32 +00:00
Code Issues Projects Releases Wiki Activity

contributor-guide: submit-changes: reword commit message instructions

Browse Source 
This should hopefully make it clearer what is expected from the
contributor.

This follows my understanding of git-commit(1)[1] where the following is
a git commit message:

"""
git commit title

git commit description
"""

I'm putting the "Fixes [YOCTO" line in "body of the commit message" so
it's understood as being different from the git commit description so
that the note admonition allowing us to have an empty commit description
doesn't apply to the "Fixes [YOCTO" line.

[1] https://www.man7.org/linux/man-pages/man1/git-commit.1.html#DISCUSSION

(From yocto-docs rev: f0f9d40a04cba684a476caaa053b6f24ade9fb99)

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(cherry picked from commit b84903a760350bd118c56ea9ce4e98039edf6e55)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
This commit is contained in:
Quentin Schulz
2025-09-18 12:24:43 +02:00
committed by Steve Sakoman
parent afd75083e9
commit 1b7cb8a80c
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/contributor-guide/submit-changes.rst
+9 -9
View File
@@ -163,7 +163,7 @@ to add the upgraded version.
this project or the open source license(s) involved. this project or the open source license(s) involved.
- Provide a single-line summary of the change and, if more - Provide a single-line summary of the change and, if more
explanation is needed, provide more detail in the body of the explanation is needed, provide more detail in the description of the
commit. This summary is typically viewable in the "shortlist" of commit. This summary is typically viewable in the "shortlist" of
changes. Thus, providing something short and descriptive that changes. Thus, providing something short and descriptive that
gives the reader a summary of the change is useful when viewing a gives the reader a summary of the change is useful when viewing a
@@ -179,23 +179,23 @@ to add the upgraded version.
git log --oneline <paths> git log --oneline <paths>
- For the body of the commit message, provide detailed information - For the commit description, provide detailed information
that describes what you changed, why you made the change, and the that describes what you changed, why you made the change, and the
approach you used. It might also be helpful if you mention how you approach you used. It might also be helpful if you mention how you
tested the change. Provide as much detail as you can in the body tested the change. Provide as much detail as you can in the commit
of the commit message. description.
.. note:: .. note::
If the single line summary is enough to describe a simple If the single line summary is enough to describe a simple
change, the body of the commit message can be left empty. change, the commit description can be left empty.
- If the change addresses a specific bug or issue that is associated - If the change addresses a specific bug or issue that is associated
with a bug-tracking ID, include a reference to that ID in your with a bug-tracking ID, include a reference to that ID in the body of the
detailed description. For example, the Yocto Project uses a commit message. For example, the Yocto Project uses a
specific convention for bug references --- any commit that addresses specific convention for bug references --- any commit that addresses
a specific bug should use the following form for the detailed a specific bug should use the following form for the body of the commit
description. Be sure to use the actual bug-tracking ID from message. Be sure to use the actual bug-tracking ID from
Bugzilla for bug-id:: Bugzilla for bug-id::
single-line summary of change single-line summary of change