Implementation: Generate a commit SHA-specific chain of custody report [Backend]
Problem to solve
This is the backend implementation issue for Generate a commit SHA-specific chain of custody report
&4608 (closed).
User experience goal
An administrator
or group owner
input a specific commit SHA into a chain of custody download prompt and receive a CSV report in the same format, but which shows the MR, pipeline, author, approver, etc for that specific commit SHA.
Intended users
- Cameron (Compliance Manager)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Sidney (Systems Administrator)
- Rachel (Release Manager)
Proposal
- Update
MergeCommitReportsController
to accept an optional commit hash parameter. - Check if the merge commit exists, if it does not then flash an error message.
- Update
MergeRequestsFinder
to find by a commit hash (merge_commit_sha
; deferringsquash_commit_sha || diff_head_sha
to a potential future iteration). - Retrieve
merge_commit_sha
,squash_commit_sha
ORdiff_head_sha
as possible values for Merge Commit SHA in the report (See discussion starting from #267628 (comment 440181389))
Edited by Aishwarya Subramanian