diff options
| author | Jafar Al-Gharaibeh <Jafaral@users.noreply.github.com> | 2021-04-10 23:07:49 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-04-10 23:07:49 -0500 |
| commit | 8435eae7bb059df82a886ef03a30c5dd620a21df (patch) | |
| tree | dfda08e5e94161501eb69a25eb8b71cef7d8200e | |
| parent | 4c3e68492b9ea264abf01b6af383783a265582cd (diff) | |
| parent | 7bd4560bbd9f79e7dc05ed189f641dc538d4d1d3 (diff) | |
Merge pull request #8440 from qlyoung/doc-describe-acceptable-commit-messages
doc: describe acceptable commit messages
| -rw-r--r-- | doc/developer/workflow.rst | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/developer/workflow.rst b/doc/developer/workflow.rst index abdbea5a9c..b4ddec10c9 100644 --- a/doc/developer/workflow.rst +++ b/doc/developer/workflow.rst @@ -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 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. .. seealso:: :ref:`signing-off` + Source File Header ------------------ |