EUVIMEDEUVIMED entdecken
Crossref

Why Are My Pull Request Descriptions Constantly Revised? Understanding Modifying Descriptions and Reviewer Suggestions

Jing Jiang, Hang Chen, Xin Tan, Zihao Liu, Li Zhang

ACM Transactions on Software Engineering and Methodology · 16.02.2026

DOI: 10.1145/3797880 ↗

Kurz gefasst

Fachartikel in der Zeitschrift ACM Transactions on Software Engineering and Methodology, online erschienen am 16.02.2026. Verfasst von Jing Jiang und 4 weiteren Autor:innen. Die Arbeit wurde bisher 1-mal zitiert (Crossref) und nennt 58 Literaturangaben.

AbstractBibliografische AngabenZitierenVerwandte Studien

Abstract (Originalsprache)

On GitHub, developers submit their code changes to projects through pull requests (PRs), which include descriptions to help reviewers understand the modifications and make informed review decisions. However, the PR descriptions provided by developers may sometimes be unclear. We find that a quarter of PR descriptions have undergone modifications. This process can be time-consuming for both developers and reviewers. Previous studies have focused on the automatic generation of PR descriptions, neglecting the importance of understanding the modification suggestions made by reviewers. Understanding these suggestions is crucial for improving PR descriptions, ensuring they can enable clear and effective communication, and speeding up the review process. To address this, we conduct an empirical study on 70,314 PRs with description modifications. We identify five categories and 17 types of information elements in description modification suggestions, such as “function summary”, “motivation”, and “related issue”. Surprisingly, 40% of suggestions are not adopted. We analyze the reasons why developers choose not to follow these suggestions, including reasons such as incorrect or difficult-to-implement suggestions. Through regression experiments, we find that modifying descriptions as suggested is positively correlated with a 4.31 times higher PR acceptance odds compared with those not following the suggestions. To enhance our understanding of what constitutes a high-quality PR description, we conducted an online survey to explore best practices for writing PR descriptions. These practices highlight the importance of clarity, context, and technical details in PRs, with eight of them being identified as highly significant. Based on these findings, we discuss recommendations for both developers and tool designers.

Zitieren

APA

Jiang, J., Chen, H., Tan, X., Liu, Z., & Zhang, L. (2026). Why Are My Pull Request Descriptions Constantly Revised? Understanding Modifying Descriptions and Reviewer Suggestions. ACM Transactions on Software Engineering and Methodology. https://doi.org/10.1145/3797880

Vancouver

Jiang J, Chen H, Tan X, Liu Z, Zhang L. Why Are My Pull Request Descriptions Constantly Revised? Understanding Modifying Descriptions and Reviewer Suggestions. ACM Transactions on Software Engineering and Methodology. 2026. doi:10.1145/3797880

BibTeX
@article{Jiang2026,
  author = {Jiang, Jing and Chen, Hang and Tan, Xin and Liu, Zihao and Zhang, Li},
  title = {Why Are My Pull Request Descriptions Constantly Revised? Understanding Modifying Descriptions and Reviewer Suggestions},
  journal = {ACM Transactions on Software Engineering and Methodology},
  year = {2026},
  doi = {10.1145/3797880}
}
Kostenlos starten →