For example, 0027b57 contains two fix commits in the same repository, and fd6b589 contains two commits across two repositories. The bug description format should be adjusted to better support such cases. A simple fix is to transform the repo and hash fields in fix into lists. However, this introduces some ambiguity into which commits belong to which repo.
A better alternative is to replace both of these fields with a commits field, which describes each of the fix commits. Fix commits would be described by an object specifying repo and hash, and could also specify some useful information for the purpose of analysis (e.g., stats, files, committer, date, etc).
For example,
0027b57
contains two fix commits in the same repository, andfd6b589
contains two commits across two repositories. The bug description format should be adjusted to better support such cases. A simple fix is to transform therepo
andhash
fields infix
into lists. However, this introduces some ambiguity into which commits belong to which repo.A better alternative is to replace both of these fields with a
commits
field, which describes each of the fix commits. Fix commits would be described by an object specifyingrepo
andhash
, and could also specify some useful information for the purpose of analysis (e.g.,stats
,files
,committer
,date
, etc).