Place for issue reference in commit message

[roman-khimov]

Current Behavior

Commit message guideline can be read as allowing header: short message, fix №XYZ or not
nspcc-dev/neo-go#3526 (comment)

Expected Behavior

Some explicit specification.

Possible Solution

Decide on whether it's allowed and document it.

[carpawell]

I would always place it in the body. No strict pros. Header says about the "code" thing to me, while body explains with some additional context (external refs).

[roman-khimov]

To me it's perfectly fine if it fits. Less lines, less things to think about.

[AnnaShaleva]

It's OK to me to use both ways. However, my personal preference matches @carpawell's opinion: use header for text description only, use body for links. It just looks more pretty to me, but it's an extremely subjective argument.

UPD: sometimes I need to put several links to PRs in the commit message, and sometimes I need to put a commit hash. Sometimes these additional links does not fit into header, and thus I put them into commit body. I love unification, and that's why I just always put all links to the commit body.