From 7fec5baa29cf349f94b4dc1945347dd3b0b35372 Mon Sep 17 00:00:00 2001 From: Javier Godoy <11554739+javier-godoy@users.noreply.github.com> Date: Sun, 4 Feb 2024 12:43:32 -0300 Subject: [PATCH] fix: clarify that footers are allowed if body if omitted Close #568 --- content/next/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/next/index.md b/content/next/index.md index 05be27f..2b014a2 100644 --- a/content/next/index.md +++ b/content/next/index.md @@ -106,7 +106,7 @@ The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL The description is a short summary of the code changes, e.g., _fix: array parsing issue when multiple spaces were contained in string_. 1. A longer commit body MAY be provided after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description. 1. A commit body is free-form and MAY consist of any number of newline separated paragraphs. -1. One or more footers MAY be provided one blank line after the body. Each footer MUST consist of +1. One or more footers MAY be provided one blank line after the body (one blank line after the description, if the body is omitted). Each footer MUST consist of a word token, followed by either a `:` or `#` separator, followed by a string value (this is inspired by the [git trailer convention](https://git-scm.com/docs/git-interpret-trailers)). 1. A footer's token MUST use `-` in place of whitespace characters, e.g., `Acked-by` (this helps differentiate