Metraipolis › archive › dc_d4da4458867d
Why Do Pull Requests Go Silent? Uncovering the Barriers to Contribution Completion in Open-Source Code Review — arXiv:2609.22625
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2609.22625
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-09T07:13:52.969Z
- SHA-256 of the archived text
59581b9f57d9981aa97c85eab2cc565423126502d2dd6ec70e563a90c5213e64- Stable URL of this page
https://metraipolis.com/documento/dc_d4da4458867d
How to cite
Why Do Pull Requests Go Silent? Uncovering the Barriers to Contribution Completion in Open-Source Code Review — arXiv:2609.22625 — arXiv (en), https://arxiv.org/abs/2609.22625 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_d4da4458867d (Metraipolis archive dc_d4da4458867d, sha256 59581b9f57d9981aa97c85eab2cc565423126502d2dd6ec70e563a90c5213e64)
BibTeX
@misc{dcd4da4458867d,
title = {Why Do Pull Requests Go Silent? Uncovering the Barriers to Contribution Completion in Open-Source Code Review — arXiv:2609.22625},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2609.22625},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_d4da4458867d; sha256 59581b9f57d9981aa97c85eab2cc565423126502d2dd6ec70e563a90c5213e64},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.22625. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Pull requests (PRs) underpin pull-based software development by enabling distributed code review and collaborative contribution in open-source projects. Yet many become inactive before integration and are eventually abandoned or closed, wasting contributor and maintainer effort. Although prior work has examined PR abandonment and review delays, less is known about the contribution types, discussion-level barriers, and post-stalling collaboration patterns associated with inactivity. We investigate which PR types most often stall, why inactivity occurs from authors' and reviewers' perspectives, and how stalling relates to later contributor and reviewer engagement. We analyzed 14,234 stalled PRs and 164,562 review comments from 19 popular GitHub repositories using stale-bot workflows. An LLM-based voting classifier categorized PRs by contribution type, while quantitative analysis was combined with qualitative coding of general and inline review discussions. Feature-enhancement and issue-fixing PRs formed the largest share, together exceeding 77% of classified stalled PRs. General comments linked stalling mainly to communication and coordination breakdowns, including missing interaction, delayed feedback, and unclear follow-up. Inline comments showed that inactivity does not always reflect disengagement: many PRs were blocked by technical or dependency issues, including failing checks, configuration problems, compatibility concerns, and environment mismatches. Only 39.56% of contributors later submitted another PR, and reviewer re-engagement with the same contributors was approximately 21%. PR inactivity is a socio-technical coordination problem involving communication, technical readiness, review ownership, and automation practices. We recommend type-aware triage, clearer review feedback, explicit ownership of next actions, CI blocker management, and cause-aware stale-bot interventions. Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-22 in cs.SE). Categorie arXiv: Software Engineering (cs.SE). Pagina del lavoro: https://arxiv.org/abs/2609.22625 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-09T07:08:15.254Z dalla pagina https://arxiv.org/catchup/cs.SE/2026-09-22?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).