Do not accept commits with no empty string after header #7

New Issue

Closed

opened 2024-06-21 09:47:21 +00:00 by alexvanin · 0 comments

alexvanin commented

2024-06-21 09:47:21 +00:00

Owner

DCO approves commit that does not contain empty line after header, e.g:

[#123] Fix issue
Signed-off-by: Developer <foo@bar.com>

Some software display this commit fine, but tig treats it as a single line header.

2024-05-24 21:31 +0300 Developer                  o [#123] Fix issue Signed-off-by: Developer <foo@bar.com>

I propose to decline such commits and require empty string after commit header.

/cc @fyrchik

DCO approves commit that does not contain empty line after header, e.g: ``` [#123] Fix issue Signed-off-by: Developer <foo@bar.com> ``` Some software display this commit fine, but `tig` treats it as a single line header. ``` 2024-05-24 21:31 +0300 Developer o [#123] Fix issue Signed-off-by: Developer <foo@bar.com> ``` I propose to decline such commits and require empty string after commit header. /cc @fyrchik

👀 1

alexvanin changed title from ~~Do not accept commits with no empty string between header and sign-off~~ to Do not accept commits with no empty string after header

2024-06-21 09:49:02 +00:00