!105 gave ProcessMRDescription the merged sha as its dedup key, shared
with ProcessCommitMessages, on the reasoning that an issue named in
both should be acted on once. That reasoning was wrong for the common
case.
ProcessCommitMessages runs first and records (issue, sha) for any
reference, including a bare #N written in passing. The description then
finds the key taken and returns without closing. So a commit that merely
mentions an issue silently disables the closing keyword in the body —
the case this feature was asked for.
Found live: krz/gitbay-ios#8 stayed open after krz/gitbay-ios!24 merged with "Closes #8" in its body, because the commit message happened to read "broke as the project moved on (#8)". The issue got "referenced in commit" and nothing else.
The key is now mr-<number>. Acting once was never the key's job — a
commit that closes the issue leaves it closed, and the issue.State != "open" check already skips it. The key's only remaining job is to stop
one merge request acting on one issue twice.
The sha parameter is gone rather than left unused.