Does Code Quality Affect Pull Request Acceptance? An empirical study
Not on the map. Why?
Abstract (arXiv)
Background. Pull requests are a common practice for contributing and reviewing contributions, and are employed both in open-source and industrial contexts. One of the main goals of code reviews is to find defects in the code, allowing project maintainers to easily integrate external contributions into a project and discuss the code contributions. Objective. The goal of this paper is to understand whether code quality is actually considered when pull requests are accepted. Specifically, we aim at understanding whether code quality issues such as code smells, antipatterns, and coding style violations in the pull request code affect the chance of its acceptance when reviewed by a maintainer of the project. Method. We conducted a case study among 28 Java open-source projects, analyzing the presence of 4.7 M code quality issues in 36 K pull requests. We analyzed further correlations by applying Logistic Regression and seven machine learning techniques (Decision Tree, Random Forest, Extremely Randomized Trees, AdaBoost, Gradient Boosting, XGBoost). Results. Unexpectedly, code quality turned out not to affect the acceptance of a pull request at all. As suggested by other works, other factors such as the reputation of the maintainer and the importance of the feature delivered might be more important than code quality in terms of pull request acceptance. Conclusions. Researchers already investigated the influence of the developers' reputation and the pull request acceptance. This is the first work investigating if quality of the code in pull requests affects the acceptance of the pull request or not. We recommend that researchers further investigate this topic to understand if different measures or different tools could provide some useful measures.
Key facts. Cited by 9 papers in the map (data through 7 Oct 2026). First posted on arXiv 25 Aug 2019.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2021: 2; 2022: 0; 2023: 2; 2024: 0; 2025: 1; 2026: 4.
9 papers.
- 2026Where Do AI Coding Agents Fail? An Empirical Study of Failed Agentic Pull Requests in GitHubcited by 10
- 2021On Wasted Contributions: Understanding the Dynamics of Contributor-Abandoned Pull Requestscited by 6
- 2026Security in the Age of AI Teammates: An Empirical Study of Agentic Pull Requests on GitHubcited by 6
- 2021Follow Your Nose -- Which Code Smells are Worth Chasing?cited by 4
- 2025Exploring the Challenges and Opportunities of AI-assisted Codebase Generationcited by 4
- 2023Predicting the First Response Latency of Maintainers and Contributors in Pull Requestscited by 3
- 2023Understanding the Helpfulness of Stale Bot for Pull-based Development: An Empirical Study of 20 Large Open-Source Projectscited by 2
- 2026Which Alert Removals are Beneficial?cited by 0
- 2026How Do AI Coding Agents Contribute to Software Development? an Empirical Study of Agentic Pull Requestscited by 0
- 2026How Do AI Coding Agents Contribute to Software Development? an Empirical Study of Agentic Pull Requests23 Jul 2026
- 2026Which Alert Removals are Beneficial?22 Mar 2026
- 2026Where Do AI Coding Agents Fail? An Empirical Study of Failed Agentic Pull Requests in GitHub21 Jan 2026
- 2026Security in the Age of AI Teammates: An Empirical Study of Agentic Pull Requests on GitHub1 Jan 2026
- 2025Exploring the Challenges and Opportunities of AI-assisted Codebase Generation11 Aug 2025
- 2023Predicting the First Response Latency of Maintainers and Contributors in Pull Requests13 Nov 2023
- 2023Understanding the Helpfulness of Stale Bot for Pull-based Development: An Empirical Study of 20 Large Open-Source Projects29 May 2023
- 2021On Wasted Contributions: Understanding the Dynamics of Contributor-Abandoned Pull Requests28 Oct 2021
- 2021Follow Your Nose -- Which Code Smells are Worth Chasing?2 Mar 2021