Abstract
In GitHub, integrators inspect submitted code changes, make evaluation decision, and close pull requests. Some pull requests may be reopened for further modification and code review. It remains unknown why some pull requests are reopened, and how they affect software development. In this paper, we conduct a case study to understand reopened pull requests. We collect 100,622 pull requests from 7 popular projects in GitHub. We study the impacts of reopened pull requests on the code review process. We then qualitatively analyze the root reasons that lead to reopening pull requests. Finally, we examine the characteristics of pull requests caused by various reasons. Our main observations are: 1) Reopened pull requests have lower acceptance rates, more comments, and longer evaluation time than non-reopened pull requests. 2) Several key reasons that lead to reopened pull request are identified such as bugs, change minds, insufficient tests, incompatible version, tests fails, and so on. 3) Reopened pull requests in different categories have various acceptance rates, comment amounts, and evaluation time. Reopened pull requests in the category rebase and change branch has the largest number of comments and the longest evaluation time. These findings provide insights to decrease reopened pull requests, develop a variety of assistant tools, and reduce the maintenance cost of open source projects.
Highlights
GitHub1 is popular among a large number of software developers around the word [1]
Reopened pull requests in the category rebase and change branch has the largest number of comments and the longest evaluation time
We study the impacts of reopened pull requests on code review (Section III)
Summary
GitHub is popular among a large number of software developers around the word [1]. GitHub provides support for pull-based development, and allow developers to make contributions flexibly and efficiently [2], [3]. A number of studies worked on reopened bugs [4]–[8], reopened issues [9] and reopened pull requests [10]. A Case Study on Open Source Projects in GitHub high accuracy predictor of reopened bugs [8]. To the best of our knowledge, characteristics of reopened pull requests have not been studied. We conduct an case study of reopened pull request in GitHub [11]. We study the impacts of reopened pull requests on code review (Section III). We study characteristics of pull requests caused by various reasons (Section V). Our study aims to answer three key questions: RQ1: What are the impacts of reopened pull requests on code review? We find several reasons that lead to reopening pull request and provide suggestions for developers to minimize reopening rate by adopting appropriate actions such as providing sufficient tests before pull requests’ submission
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
