Pull Request Governance in Open Source Communities
Abstract
Pull requests facilitate inclusion and improvement of contributions in distributed software projects, especially in open source communities. An author makes a pull request to present a contribution as a candidate for inclusion in a code base. The request is inspected by maintainers and reviewers. The initiated process of review and collaborative improvement can be loaded with debates, opinions, and emotions. It heavily influences the atmosphere in the community. It can demotivate and detract contributors or it can fail to guard the code quality. Both problems put the existence of a community at risk. This mixed methods study aims to elucidate the mechanisms of evaluating pull requests in diverse open source software communities from the perspectives of developers and maintainers. We interviewed 30 participants from five different communities and conducted a survey with N=387 respondents. The data shows that acceptance of contributions in open source depends not only on technical criteria, but also significantly on social and strategic aspects. As a result, we identify three governance styles for pull requests: (1) protective, (2) equitable, and (3) lenient. While the protective style values trustworthiness and reliability of the contributor, the lenient style believes in creating a positive and welcoming environment where contributors are mentored to evolve contributions until the community standards are met. Each of the governance styles safeguards the quality of the project…
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
The inclusion criterion for GenAI governance was fixed before document analysis began and stayed stable throughout screening, not shaped by findings.
“We fixed this inclusion criterion before document analysis began, building on prior definitions of OSS contribution governance [1, 11, 12]. The criterion stayed stable throughout screening; we only refined how it applied to borderline cases, so it was not shaped by our findings.”
From To Ban or Not to Ban? How Open Source Projects Govern GenAI Contributions (2026) · cites this paper as [1]
Cites
Saturation in qualitative research: exploring its conceptualization and operationalization
Saunders, B., Sim, J., Kingstone, T., Baker, S., Waterfield, J., Bartlam, B., Burroughs, H., & Jinks, C. (2018) · Quality & Quantity · doi:10.1007/s11135-017-0574-8 · Cited by 12,033 · cited 1× · see citing works
“We stopped interviewing after attaining saturation [11]”
Social Capital: Prospects for a New Concept
Adler, P. S., & Kwon, S.-W. (2002) · The Academy of Management Review · doi:10.2307/4134367 · Cited by 9,665 · see citing works
Lakhani, K. R., & Wolf, R. G. (2003) · doi:10.2139/ssrn.443040 · Cited by 1,531 · see citing works
Rejecting or Accepting Parameter Values in Bayesian Estimation
Kruschke, J. K. (2018) · Advances in Methods and Practices in Psychological Science · doi:10.1177/2515245918771304 · Cited by 734 · see citing works
Measure it? Manage it? Ignore it? software practitioners and technical debt
Ernst, N. A., Bellomo, S., Ozkaya, I., Nord, R. L., & Gorton, I. (2015) · Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering · doi:10.1145/2786805.2786848 · Cited by 260 · see citing works
Intrinsic motivation in open source software development
Bitzer, J., Schrettl, W., & Schröder, P. J. H. (2007) · Journal of Comparative Economics · doi:10.1016/j.jce.2006.10.001 · Cited by 163 · see citing works
Flagged first, then by citations
Cited by
Sorted by citations
To Ban or Not to Ban? How Open Source Projects Govern GenAI Contributions
Yang, W., He, R., & Zhou, M. (2026) · Proceedings of the 41st IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/3832783.3837448 · Cited by 1 · see citing works
Making AI Visible, Not Vanished: How AI Policies Reshape Developer Experience on GitHub
Chen, Y., Zimmermann, T., & Trinkenreich, B. (2026) · arXiv · doi:10.48550/arxiv.2608.03329
Do AI-Generated Pull Requests Get Rejected More? (Yes but Why?)
Wang, Y., & Yang, Z. (2026) · Proceedings of the 23rd International Conference on Mining Software Repositories · doi:10.1145/3793302.3793568
- Authors
- Alami, A., Pardo, R., Cohn, M. L., & Wasowski, A.
- Affiliations
- IT University of Copenhagen, Copenhagen, Denmark
- ORCID
- Alami, Adam
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2022-12-01
- Volume
- 48
- Issue
- 12
- Pages
- 4838-4856
- ISSN
- 0098-5589
- 1939-3520
- 2326-3881
- Cited by
- 15
- References
- 6
- Licence
- Funders
- H2020 European Institute of Innovation and Technology (732287)
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review