2021 IEEE/ACM 43rd International Conference on Software Engineering (ICSE) 2021
DOI: 10.1109/icse43902.2021.00027
|View full text |Cite
|
Sign up to set email alerts
|

Towards Automating Code Review Activities

Abstract: Code reviews are popular in both industrial and open source projects. The benefits of code reviews are widely recognized and include better code quality and lower likelihood of introducing bugs. However, since code review is a manual activity it comes at the cost of spending developers time on reviewing their teammates code.Our goal is to make the first step towards partially automating the code review process, thus, possibly reducing the manual costs associated with it. We focus on both the contributor and

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

1
63
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
5
2

Relationship

1
6

Authors

Journals

citations
Cited by 71 publications
(70 citation statements)
references
References 34 publications
(34 reference statements)
1
63
0
Order By: Relevance
“…This resulted in a list of 4,901 projects. We also mined the six Gerrit [1] installations used in [46] containing code review data about 6,388 projects.…”
Section: Fine-tuning Datasetsmentioning
confidence: 99%
See 3 more Smart Citations
“…This resulted in a list of 4,901 projects. We also mined the six Gerrit [1] installations used in [46] containing code review data about 6,388 projects.…”
Section: Fine-tuning Datasetsmentioning
confidence: 99%
“…Overall, we mined 382,955 valid triplets from GitHub and Gerrit using the pipeline from [46] that we summarize in the following (see [46] for additional details). We target triplets in which a comment 𝑐 𝑛𝑙 has been posted by a reviewer on a method 𝑚 𝑠 .…”
Section: Fine-tuning Datasetsmentioning
confidence: 99%
See 2 more Smart Citations
“…However, the understanding of automatic code review is not the only one, Tufan [38] proposes a method, learning the code changes recommended by reviewer, to implement them in the original code automatically. In other words, they are trying to make a map from the original code file to the revised code file, which is totally different from the opinion that Shi [9] hold.…”
Section: Automatic Code Reviewmentioning
confidence: 99%