Closed
Description
The original commit message in nodejs/node#41490 was:
commit f042c61749a34565ab57b5ed5f7c89ab9e894494
Author: Tobias Nießen <[email protected]>
Date: Tue Jan 11 20:38:00 2022 +0000
src: gracefully handle errors in GetX509NameObject
Co-authored-by: Anna Henningsen <[email protected]>
However, git node land
added metadata at the end without incorporating the Co-authored-by
line:
commit 721cc6b5e2d6f4112b56ee5ead19ddaeb99ac7a6
Author: Tobias Nießen <[email protected]>
Date: Tue Jan 11 20:38:00 2022 +0000
src: gracefully handle errors in GetX509NameObject
Co-authored-by: Anna Henningsen <[email protected]>
PR-URL: https://github.com/nodejs/node/pull/41490
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
GitHub does not recognize the Co-authored-by
line since there is an empty line between that and the metadata lines at the end. I didn't know this and I only coincidentally noticed that GitHub did not display the correct commit authorship after pushed.
I have force-pushed the correct the commit message:
commit 4dd1f42df6ee34c1a5456862647092cb9686ec9a (HEAD -> master, upstream/master)
Author: Tobias Nießen <[email protected]>
Date: Tue Jan 11 20:38:00 2022 +0000
src: gracefully handle errors in GetX509NameObject
PR-URL: https://github.com/nodejs/node/pull/41490
Co-authored-by: Anna Henningsen <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Both messages pass core-validate-commit
.
Other examples: