proxmox-mirrors/mirror_frr
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_frr synced 2025-04-29 18:10:23 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #8440 from qlyoung/doc-describe-acceptable-commit-messages

Browse Source 
doc: describe acceptable commit messages
This commit is contained in:
Jafar Al-Gharaibeh 2021-04-10 23:07:49 -05:00 committed by GitHub
commit 8435eae7bb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/developer/workflow.rst
View File

@ -500,10 +500,22 @@ made. For example, a change in :file:`bgpd/rfapi` would be formatted as::
The first line should be no longer than 50 characters. Subsequent lines should The first line should be no longer than 50 characters. Subsequent lines should
be wrapped to 72 characters. be wrapped to 72 characters.
The purpose of commit messages is to briefly summarize what the commit is
changing. Therefore, the extended summary portion should be in the form of an
English paragraph. Brief examples of program output are acceptable but if
present should be short (on the order of 10 lines) and clearly demonstrate what
has changed. The goal should be that someone with only passing familiarity with
the code in question can understand what is being changed.
Commit messages consisting entirely of program output are *unacceptable*. These
do not describe the behavior changed. For example, putting VTYSH output or the
result of test runs as the sole content of commit messages is unacceptable.
You must also sign off on your commit. You must also sign off on your commit.
.. seealso:: :ref:`signing-off` .. seealso:: :ref:`signing-off`
Source File Header Source File Header
------------------ ------------------