Skip to content

Record patch_id_sha on new MergeRequestDiffs

What does this MR do and why?

When a new MergeRequestDiff record is created, capture its patch_id_sha, which acts as a unique "fingerprint" for the diff.

Similar to !131205 (merged)

Related to #424542 (closed)

Merge request reports