Appendix of "Revisiting the Effect of Branch Handling Strategies on Change Recommendation"

<p>This is the dataset of the paper &quot;Revisiting the Effect of Branch Handling Strategies on Change Recommendation&quot;,&nbsp;presented at ICPC 2022.</p> <p><strong>Files Overview</strong></p> <ul> <li>`path/to/merge_result.db`: SQLite database for the results of Imp_merge.</li> <li>`path/to/no_merge_result.db`: SQLite database for the results of Imp_no_merge.</li> </ul> <p><strong>Database Schema</strong></p> <ul> <li>Table: result <ul> <li>id: ID</li> <li>hexsha: the commit SHA-1</li> <li>algorithm_type: the algorithm used (SINGLE or OTHERS)</li> <li>history_type: the branch handling strategy used (FULL, FIRST_PARENTS, or BOTH). BOTH is used in case two strategies used the same commits.</li> <li>result_type: prediction result (SUCCESS, FAILURE, NO_PREDICTION, or NO_RULE). NO_RULE is used in case of no prediction and no rule.</li> <li>answer_file_name: the oracle filename</li> </ul> </li> <li>Table: prediction <ul> <li>id: ID</li> <li>result_id: refers to result.id</li> <li>file_name: the predicted filename</li> </ul> </li> <li>Table: query <ul> <li>id: ID</li> <li>result_id: refers to result.id</li> <li>file_name: the filename used as the query</li> </ul> </li> <li>Table: used_commit <ul> <li>id: ID</li> <li>result_id: refers to result.id</li> <li>hexsha: the commit SHA-1 to be used for recommendation</li> </ul> </li> <li>Table: rule <ul> <li>id: ID</li> <li>result_id: refers to result.id</li> <li>conclusion: the filename at the conclusion part</li> <li>confidence: the confidence value</li> <li>support: the support value</li> </ul> </li> <li>Table: rule_term (the condition part of a rule) <ul> <li>id: ID</li> <li>rule_id: refers to rule.id</li> <li>file_name: the filename at the condition part</li> </ul> </li> </ul>