AgenticFlict: A Large-Scale Dataset of Merge Conflicts in AI Coding Agent Pull Requests on GitHub
Open accessThe DOI matches its Crossref record; 52 of the 70 references it cites were found in a registry or an index, and 9 are not checked yet; 6 of the 28 sources its claims cite were checked for support.
Abstract
Software Engineering 3.0 marks a paradigm shift in software development, in which AI coding agents are no longer just assistive tools but active contributors. While prior empirical studies have examined productivity gains and acceptance patterns in AI-assisted development, the challenges associated with integrating agent-generated contributions remain less understood. In particular, merge conflicts, a fundamental aspect of collaborative software development, remain underexplored in this context. In this paper, we present AgenticFlict, a large-scale dataset of textual merge conflicts in AI coding agent pull requests (Agentic PRs). The dataset comprises 142K+ Agentic PRs collected from 59K+ repositories, of which 107K+ are successfully processed through deterministic merge simulation. Our pipeline identifies 29K+ PRs exhibiting merge conflicts, yielding a conflict rate of 27.67%, and extracts 336K+ fine-grained conflict regions across these instances. Our preliminary exploratory analysis indicates that merge conflicts are both frequent and often substantial in AI-generated contributions, with noticeable variation across agents, emphasizing the need to better understand and manage integration challenges in AI-assisted software development. The dataset, code and supplementary materials are available in zenodo: 10.5281/zenodo.19396916
Verified 2026-11-20 · 9 references not checked yet
Overview
CoChat Summary
TL;DR
AgenticFlict is a large-scale dataset of textual merge conflicts in AI coding agent pull requests on GitHub. Using deterministic merge simulation on 107,026 PRs from 59,412 repositories, the paper finds 29,609 conflicting PRs (27.67%) and 336,380 conflict regions.
Key findings
- From 142,652 Agentic PRs, the authors successfully simulated merges for 107,026 PRs, a 75.03% success rate; 35,626 PRs were excluded due to missing references or inaccessible repositories.
- Among successfully simulated PRs, 29,609 had textual merge conflicts, for a conflict rate of 27.67%.
- Conflicting PRs affected an average of 4.36 files per PR (median 2.00), 11.36 conflict regions per PR, and 540.42 conflicting lines per PR; the dataset contains 336,380 total conflict regions.
- Conflict rates varied across five AI coding agents: Copilot 15.24%, Cursor 19.75%, Devin 22.85%, Claude_Code 25.93%, and OpenAI_Codex 31.85%. Conflict severity also showed heavy-tailed distributions, and larger PRs had higher conflict rates; for example, median churn of 2 lines corresponded to about 9.9% conflict rate, while median churn of 25 lines corresponded to nearly 30%.
Methods
- The study builds AgenticFlict from the AIDev dataset: after filtering to open or closed-but-unmerged PRs, it retains 142,652 candidate PRs spanning 59,412 repositories and five AI coding agents.
- For each PR, the pipeline retrieves GitHub metadata, prepares a local repository clone, and performs deterministic merge simulation with Git (`git merge -no-commit -no-ff <headRefOid>`), using open PR state or reconstructed closure-time base commits for closed unmerged PRs.
- When merges fail, the authors parse Git conflict markers to extract file-level and region-level conflict metadata, including file paths, line spans, conflict counts, and severity metrics; they also analyze conflict rates by agent and by PR size (code churn).
Limitations
- The paper states that 35,626 PRs were unrecoverable because of permanently missing references, repository deletion, or access limitations, reducing coverage.
- It states that the method captures textual conflict markers only, so it does not account for logical inconsistencies or post-merge defects.
- It states that focusing on open and closed (unmerged) PRs may miss conflicts that occurred and were resolved before merge; this is a stated limitation.
- Evident from the text: the dataset is built on AIDev and may overrepresent repositories that actively adopt AI tools, so the findings may not generalize to all open-source or industrial settings.
Model-written summary. Check it against the paper before relying on it.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
2 Valid · 3 Not valid · 12 Not checked · 47 Own results and interpretations
At least one cited source doesn’t support this claim or points to a different paper, and none confirmed it — see the verdicts below.
In the paper
“The dataset contains 932,791 Agentic PRs.”
What the sources say
- Disputedcites [34] [34] Hao Li, Haoxiang Zhang, and Ahmed E. Hassan. 2025. The Rise of AI Teammates in Software Engineering (SE) 3.0: How Autonomous Coding Agents Are Reshaping Software Engineering. arXiv preprint arXiv:2507.15003 (2025). - sourceExperimental — accuracy not yet measured
The Dataset Overview (Section 3.2, pp. 6–7) states that the full AIDev dataset contains 456,535 pull requests, not 932,791. Table 3 confirms the 456,535 total. (LLM, conf=0.94)
Checked by a reasoning model — may be wrong.
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: unclear — It is unclear whether the paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Disputed
The cited sources that could be checked couldn’t confirm or dispute this claim.
In the paper
“To the best of our knowledge, AgenticFlict is the first largescale dataset of textual merge conflicts in Agentic PRs.”
What the sources say
- Not checked — no full text of the sourcecites [49] [49] Bowen Shen and Na Meng. 2024. ConflictBench: A benchmark to evaluate software merge tools. Journal of Systems and Software 214 (2024), 112084. doi:10. 1016/j.jss.2024.112084 - source
- Could not verifycites [34] [34] Hao Li, Haoxiang Zhang, and Ahmed E. Hassan. 2025. The Rise of AI Teammates in Software Engineering (SE) 3.0: How Autonomous Coding Agents Are Reshaping Software Engineering. arXiv preprint arXiv:2507.15003 (2025). - sourceExperimental — accuracy not yet measured
The Introduction (pp. 2–3) describes AIDev, a large-scale dataset of Agentic PRs, not AgenticFlict. A search for AgenticFlict and textual merge conflicts found no passage establishing that AgenticFlict is a dataset or the first of its kind; the Code Review Dynamics section (p. 14) mentions resolving merge conflicts only as a possible future capability. (LLM, conf=0.76)
hedged- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
The cited sources that could be checked couldn’t confirm or dispute this claim.
In the paper
“As a result, integration friction due to textual conflicts is not explicitly captured in most pull request datasets.”
What the sources say
- Could not verifycites [2] [2] Adam Alami and Neil Ernst. 2025. Human and Machine: How Software Engineers Perceive and Engage with AI-Assisted Code Reviews Compared to Their Peers. In 2025 IEEE/ACM 18th International Conference on Cooperative and Human Aspects of Software Engineering (CHASE) . 63-74. doi:10.1109/CHASE66643.2025.00016 - sourceExperimental — accuracy not yet measured
Our copy is a 20-interview qualitative study; no passage addresses pull request datasets or what they do or do not capture. Searched 'integration friction', 'textual conflicts', 'pull request datasets', 'dataset mining code review emotion/sentiment' — the closest material is the Limitations section (anonymous Prolific review, communities' differing PR review styles 'lenient' to 'protective' [6], [7]), the Feedback constructiveness section crediting Gonçalves et al. [79] with reporting that negative feedback causes interpersonal conflicts, and Related Work on bots as textual interfaces — none of which states the claim's point about dataset coverage. Nothing contrary is said either, so this is absence rather than dispute. (LLM, conf=0.70)
- Could not verifycites [24] [24] Ismail Sergen Göçmen, Ahmed Salih Cezayir, and Eray Tüzün. 2025. Enhanced code reviews using pull request based change impact analysis. Empirical Software Engineering 30, 3 (2025), 64. doi:10.1007/s10664-024-10600-2 - sourceExperimental — accuracy not yet measured
Our copy is a qualitative think-aloud study of 25 observed review sessions across 10 reviewers (Data Collection, p. 3; Limitations table and text, p. 5); it never discusses pull request datasets as a data source's coverage, nor merge/textual conflicts or 'integration friction'. The nearest statement is in Implications and Recommendations (p. 11), where prior methods including mining software repositories are said to have 'limitations in capturing critical factors such as context, priorities, interactions among reviewers, and their knowledge of the software system being reviewed' — a different point that does not mention textual conflicts or datasets. Searches for 'merge conflict / textual conflict / integration', 'pull request datasets', and 'mining datasets limitations' returned no passage addressing the claim, so the source neither supports nor contradicts it. (LLM, conf=0.72)
- Not checked — no full text of the sourcecites [25] [25] Pavlína Wurzel Gonçalves, Pooja Rani, Margaret-Anne Storey, Diomidis Spinellis, and Alberto Bacchelli. 2025. Code Review Comprehension: Reviewing Strategies Seen Through Code Comprehension Theories. In 2025 IEEE/ACM 33rd International Conference on Program Comprehension (ICPC) . 589-601. doi:10.1109/ ICPC66645.2025.00068 - source
- Not checked — no full text of the sourcecites [33] [33] Oleksii Kononenko, Olga Baysal, and Michael W. Godfrey. 2016. Code review quality: how developers see it. In Proceedings of the 38th International Conference on Software Engineering (Austin, Texas) (ICSE '16) . Association for Computing Machinery, New York, NY, USA, 1028-1038. doi:10.1145/2884781.2884840 - source
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Could not verify
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“extracts 336K+ fine-grained conflict regions across these instances”
- Also stated in: § 1 Introduction · plain
“extracts 336,380 fine-grained conflict regions across these instances”
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Also stated in: § 1 Introduction · plain
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“The dataset comprises 142K+ Agentic PRs collected from 59K+ repositories”
- Also stated in: § 1 Introduction · plain
“The dataset comprises 142,652 Agentic PRs collected from 59,412 repositories”
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Also stated in: § 1 Introduction · plain
21 more claims
Create a free account to see all 64 claims and to verify the 8 references still open.
- It may state two separate claims as one. 25
- Probably not a substantial claim. 17
- The quote only partly states this claim. 2
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
Each contradiction between two passages listed here was confirmed by an independent check.
Rated minor: it would not touch a result — a value no result rests on, a p-value that stays on the same side of the significance level, or a conflict that is clerical, resolved elsewhere in the paper, or outside its own findings.
In the paper
§ 4 Exploratory Empirical Analysis
“In contrast, OpenAI Codex shows the highest conflict rate at 32.31%, more than double that of Copilot.”
§ 4 Exploratory Empirical Analysis
“| OpenAI_Codex | 73856 | 23520 | 31.85 | 31.51 | 32.18 |”
Rated minor: it would not touch a result — a value no result rests on, a p-value that stays on the same side of the significance level, or a conflict that is clerical, resolved elsewhere in the paper, or outside its own findings.
In the paper
§ 4 Exploratory Empirical Analysis
“Copilot exhibits the lowest conflict rate at 15.43%, followed by Cursor (20.06%) and Devin (23.04%).”
§ 4 Exploratory Empirical Analysis
“| Copilot | 16954 | 2583 | 15.24 | 14.69 | 15.78 |”
Citations
Cites
The promises and perils of mining GitHub
Kalliamvakou, E., Gousios, G., Blincoe, K., Singer, L., German, D. M., & Damian, D. (2014) · Proceedings of the 11th Working Conference on Mining Software Repositories · doi:10.1145/2597073.2597074 · Cited by 770 · cited 1×
“To further examine the nature of these conflicts, we analyze conflict severity, measured as the number of conflicting lines per PR. Figure 4 shows the distribution of conflict severity across agents on a logarithmic scale.”
Vaithilingam, P., Zhang, T., & Glassman, E. L. (2022) · CHI Conference on Human Factors in Computing Systems Extended Abstracts · doi:10.1145/3491101.3519665 · Cited by 660
An exploratory study of the pull-based software development model
Gousios, G., Pinzger, M., & Deursen, A. V. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568260 · Cited by 628 · cited 2×
“In addition, conflict behavior may vary across programming languages, repository sizes, and development practices.”
The GHTorent dataset and tool suite
Gousios, G. (2013) · 2013 10th Working Conference on Mining Software Repositories (MSR) · doi:10.1109/msr.2013.6624034 · Cited by 399 · cited 1×
“This approach follows established practices in large-scale mining of GitHub data [17, 26, 48] and aligns with GitHub’s Terms of Service governing code redistribution [21].”
Towards a Big Data Curated Benchmark of Inter-project Code Clones
Svajlenko, J., Islam, J. F., Keivanloo, I., Roy, C. K., & Mia, M. M. (2014) · 2014 IEEE International Conference on Software Maintenance and Evolution · doi:10.1109/icsme.2014.77 · Cited by 339 · cited 1×
“This approach follows established practices in large-scale mining of GitHub data [17, 26, 48] and aligns with GitHub’s Terms of Service governing code redistribution [21].”
The promises and perils of mining git
Bird, C., Rigby, P. C., Barr, E. T., Hamilton, D. J., German, D. M., & Devanbu, P. (2009) · 2009 6th IEEE International Working Conference on Mining Software Repositories · doi:10.1109/msr.2009.5069475 · Cited by 311 · cited 2×
“Certain merge simulation failures may arise when repositories have been deleted or historical commits are no longer reachable due to force-pushes or history rewrites [5, 9, 45].”
The Impact of AI on Developer Productivity: Evidence from GitHub Copilot
Peng, S., Kalliamvakou, E., Cihon, P., & Demirer, M. (2023) · arXiv · doi:10.48550/arxiv.2302.06590 · Cited by 287
Productivity Assessment of Neural Code Completion
Ziegler, A., Kalliamvakou, E., Li, X. A., Rice, A., Rifkin, D., Simister, S., Sittampalam, G., & Aftandilian, E. (2022) · Proceedings of the 6th ACM SIGPLAN International Symposium on Machine Programming · doi:10.1145/3520312.3534864 · Cited by 200 · cited 1×
“More recent empirical research has begun to investigate development efficiency and code review dynamics in AI-assisted settings [38, 54, 57].”
Code review quality: how developers see it
Kononenko, O., Baysal, O., & Godfrey, M. W. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884840 · Cited by 183 · cited 2×
“In addition, conflict behavior may vary across programming languages, repository sizes, and development practices.”
A Systematic Mapping Study of Software Development With GitHub
Cosentino, V., Canovas Izquierdo, J. L., & Cabot, J. (2017) · IEEE Access · doi:10.1109/access.2017.2682323 · Cited by 168
Early Detection of Collaboration Conflicts and Risks
Brun, Y., Holmes, R., Ernst, M. D., & Notkin, D. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2013.28 · Cited by 82 · cited 4×
“Brun et al. [7] demonstrate that collaboration conflicts are frequent and costly in distributed development environments.”
InfluentialAI-Assisted Assessment of Coding Practices in Modern Code Review
Vijayvergiya, M., Salawa, M., Budiselić, I., Zheng, D., Lamblin, P., Ivanković, M., Carin, J., Lewko, M., Andonov, J., Petrović, G., et al. (2024) · ACM International Conference on AI-Powered Software (AIware) · doi:10.1145/3664646.3665664 · Cited by 70 · cited 1×
“More recent empirical research has begun to investigate development efficiency and code review dynamics in AI-assisted settings [38, 54, 57].”
Predicting Merge Conflicts in Collaborative Software Development
Owhadi-Kareshk, M., Nadi, S., & Rubin, J. (2019) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1109/esem.2019.8870173 · Cited by 68
On the Nature of Merge Conflicts: A Study of 2,731 Open Source Java Projects Hosted by GitHub
Ghiotto, G., Murta, L., Barros, M., & van der Hoek, A. (2020) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2018.2871083 · Cited by 67 · cited 1×
“While Shen and Meng [47] introduced ConflictBench as a dedicated benchmark for studying conflicts, other existing datasets have typically emerged as secondary artifacts of broader studies on collaborative development [11, 18, 49].”
DevGPT: Studying Developer-ChatGPT Conversations
Xiao, T., Treude, C., Hata, H., & Matsumoto, K. (2024) · Proceedings of the 21st International Conference on Mining Software Repositories · doi:10.1145/3643991.3648400 · Cited by 56
Improving early detection of software merge conflicts
Guimarães, M. L., & Silva, A. R. (2012) · 2012 34th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2012.6227180 · Cited by 56 · cited 1×
“Prior research has shown that merge conflicts introduce substantial coordination overhead and negatively impact developer productivity [7, 28, 36, 42, 53].”
Agentic Refactoring: An Empirical Study of AI Coding Agents
Horikawa, K., Li, H., Kashiwa, Y., Adams, B., Iida, H., & Hassan, A. E. (2026) · ACM Transactions on Software Engineering and Methodology · doi:10.48550/arxiv.2511.04824 · Cited by 55
Software Practitioner Perspectives on Merge Conflicts and Resolutions
McKee, S., Nelson, N., Sarma, A., & Dig, D. (2017) · 2017 IEEE International Conference on Software Maintenance and Evolution (ICSME) · doi:10.1109/icsme.2017.53 · Cited by 53 · cited 1×
“Prior research has shown that merge conflicts introduce substantial coordination overhead and negatively impact developer productivity [7, 28, 36, 42, 53].”
Understanding semi-structured merge conflict characteristics in open-source Java projects
Accioly, P., Borba, P., & Cavalcanti, G. (2018) · Empirical Software Engineering · doi:10.1007/s10664-017-9586-1 · Cited by 48
Clone-Based Variability Management in the Android Ecosystem
Businge, J., Openja, M., Nadi, S., Bainomugisha, E., & Berger, T. (2018) · 2018 IEEE International Conference on Software Maintenance and Evolution (ICSME) · doi:10.1109/icsme.2018.00072 · Cited by 38 · cited 1×
“Certain merge simulation failures may arise when repositories have been deleted or historical commits are no longer reachable due to force-pushes or history rewrites [5, 9, 45].”
Self-citationProgram merge conflict resolution via neural transformers
Svyatkovskiy, A., Fakhoury, S., Ghorbani, N., Mytkowicz, T., Dinella, E., Bird, C., Jang, J., Sundaresan, N., & Lahiri, S. K. (2022) · Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3540250.3549163 · Cited by 38 · cited 1×
“While Shen and Meng [47] introduced ConflictBench as a dedicated benchmark for studying conflicts, other existing datasets have typically emerged as secondary artifacts of broader studies on collaborative development [11, 18, 49].”
Challenges of Resolving Merge Conflicts: A Mining and Survey Study
Vale, G., Hunsen, C., Figueiredo, E., & Apel, S. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3130098 · Cited by 38
Reuse and maintenance practices among divergent forks in three software ecosystems
Businge, J., Openja, M., Nadi, S., & Berger, T. (2022) · Empirical Software Engineering · doi:10.1007/s10664-021-10078-2 · Cited by 37
Self-citationOn the Use of Agentic Coding: An Empirical Study of Pull Requests on GitHub
Watanabe, M., Li, H., Kashiwa, Y., Reid, B., Iida, H., & Hassan, A. E. (2026) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3798166 · Cited by 34
Cui, K. Z., Demirer, M., Jaffe, S., Musolff, L., Peng, S., & Salz, T. (2026) · Management Science · doi:10.1287/mnsc.2025.00535 · Cited by 28
A Characterization Study of Merge Conflicts in Java Projects
Shen, B., Gulzar, M. A., He, F., & Meng, N. (2022) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3546944 · Cited by 25 · cited 1×
“In practice, integrating code in a collaborative environment is rarely smooth due to conflicts [8, 10, 39, 46].”
Planning for untangling: predicting the difficulty of merge conflicts
Brindescu, C., Ahmed, I., Leaño, R., & Sarma, A. (2020) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3377811.3380344 · Cited by 23 · cited 1×
“By making these conflict patterns observable at scale, AgenticFlict provides a foundation for studying how AI agents interact with collaborative development workflows.”
PatchTrack: A comprehensive analysis of ChatGPT’s influence on pull request outcomes
Ogenrwot, D., & Businge, J. (2026) · Empirical Software Engineering · doi:10.1007/s10664-026-10869-5 · Cited by 22 · cited 3×
“Prior work has examined how developers interact with AI-generated code and the impact of these tools on productivity and software quality [34, 37, 38, 50, 51].”
InfluentialSelf-citationAlami, A., & Ernst, N. (2025) · 2025 IEEE/ACM 18th International Conference on Cooperative and Human Aspects of Software Engineering (CHASE) · doi:10.1109/chase66643.2025.00016 · Cited by 15
Enhanced code reviews using pull request based change impact analysis
Göçmen, İ. S., Cezayir, A. S., & Tüzün, E. (2025) · Empirical Software Engineering · doi:10.1007/s10664-024-10600-2 · Cited by 14
Software Ecosystems: Tooling and Analytics
Mens, T., Roover, C. D., & Cleve, A. (2023) · Springer eBooks · doi:10.1007/978-3-031-36060-2 · Cited by 14
PaReco: patched clones and missed patches among the divergent variants of a software family
Ramkisoen, P. K., Businge, J., van Bladel, B., Decan, A., Demeyer, S., De Roover, C., & Khomh, F. (2022) · Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3540250.3549112 · Cited by 10 · cited 1×
“To further examine the nature of these conflicts, we analyze conflict severity, measured as the number of conflicting lines per PR. Figure 4 shows the distribution of conflict severity across agents on a logarithmic scale.”
Self-citationConflictBench: A benchmark to evaluate software merge tools
Shen, B., & Meng, N. (2024) · Journal of Systems and Software · doi:10.1016/j.jss.2024.112084 · Cited by 10 · cited 1×
“While Shen and Meng [47] introduced ConflictBench as a dedicated benchmark for studying conflicts, other existing datasets have typically emerged as secondary artifacts of broader studies on collaborative development [11, 18, 49].”
Causes of merge conflicts: a case study of ElasticSearch
Mahmood, W., Chagama, M., Berger, T., & Hebig, R. (2020) · Proceedings of the 14th International Working Conference on Variability Modelling of Software-Intensive Systems · doi:10.1145/3377024.3377047 · Cited by 10 · cited 1×
“The dataset comprises over 142K Agentic PRS collected from more than 59K repositories, with over 107K successfully analyzed through deterministic merge simulation resulting in over 29K (27.67”
InfluentialBlockchain-Oriented Software Variant Forks: A Preliminary Study
Rocha, H., & Businge, J. (2022) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner53432.2022.00139 · Cited by 10
Self-citationAgentic Software Engineering: Foundational Pillars and a Research Roadmap
Hassan, A. E., Li, H., Lin, D., Adams, B., Chen, T.-H., Kashiwa, Y., & Qiu, D. (2025) · arXiv · doi:10.48550/arxiv.2509.06216 · Cited by 7 · cited 1×
“This evolution reflects a broader shift from assistive tooling toward active collaboration, often described as Software Engineering 3.0 [29, 30, 40].”
InfluentialTowards Merge Conflict Resolution by Combining Existing Lines of Code
Campos, H. D. S., Ghiotto, G., Barros, M. D. O., van der Hoek, A., & Murta, L. (2022) · Brazilian Symposium on Software Engineering · doi:10.1145/3555228.3555229 · Cited by 5 · cited 1×
“While Shen and Meng [47] introduced ConflictBench as a dedicated benchmark for studying conflicts, other existing datasets have typically emerged as secondary artifacts of broader studies on collaborative development [11, 18, 49].”
Refactoring-Aware Patch Integration Across Structurally Divergent Java Forks
Ogenrwot, D., & Businge, J. (2025) · IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM) · doi:10.1109/scam67354.2025.00010 · Cited by 5
Self-citationCode Review Comprehension: Reviewing Strategies Seen Through Code Comprehension Theories
Gonçalves, P. W., Rani, P., Storey, M.-A., Spinellis, D., & Bacchelli, A. (2025) · 2025 IEEE/ACM 33rd International Conference on Program Comprehension (ICPC) · doi:10.1109/icpc66645.2025.00068 · Cited by 4 · cited 1×
“In addition, conflict behavior may vary across programming languages, repository sizes, and development practices.”
On the Use of Agentic Coding: An Empirical Study of Pull Requests on GitHubPreprint
Watanabe, M., Li, H., Kashiwa, Y., et al. (2025) · arXiv (Cornell University) · doi:10.48550/arxiv.2509.14745 · Cited by 4
PatchTrack: Analyzing ChatGPT's Impact on Software Patch Decision-Making in Pull Requests
Ogenrwot, D., & Businge, J. (2024) · Proceedings of the 39th IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/3691620.3695338 · Cited by 3 · cited 2×
“Prior work has examined how developers interact with AI-generated code and the impact of these tools on productivity and software quality [34, 37, 38, 50, 51].”
InfluentialSelf-citationStructural and Connectivity Patterns in the Maven Central Software Dependency Network
Ogenrwot, D., Businge, J., & Arifuzzaman, S. (2025) · Communications in computer and information science · doi:10.1007/978-3-032-08649-5_9 · Cited by 2
Self-citationBehind Developer Contributions on Conflicting Merge Scenarios
Vale, G., Fernandes, E., Figueiredo, E., & Apel, S. (2023) · 2023 IEEE 23rd International Working Conference on Source Code Analysis and Manipulation (SCAM) · doi:10.1109/scam59687.2023.00014 · Cited by 1 · cited 1×
“By making these conflict patterns observable at scale, AgenticFlict provides a foundation for studying how AI agents interact with collaborative development workflows.”
Analyzing Variant Forks of Software Repositories from Social Coding Platforms
Businge, J., Abdi, M., & Demeyer, S. (2023) · Software Ecosystems · doi:10.1007/978-3-031-36060-2_6 · Cited by 1 · cited 1×
“In practice, integrating code in a collaborative environment is rarely smooth due to conflicts [8, 10, 39, 46].”
Self-citationTowards a Feasible Evaluation Function for Search-Based Merge Conflict Resolution
de Souza Campos, H., de Menezes, G. G. L., de Oliveira Barros, M., van der Hoek, A., & Gresta Paulino Murta, L. (2026) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3748256 · Cited by 1
Сучасний підхід до проблеми виникнення університету як соціокультурного феномену
Aslan (2018) · Electronic Volyn National University Institutional Repository · doi:10.5281/zenodo
Li, H., Zhang, H., & Hassan, A. E. (2025) · arXiv · doi:10.48550/arxiv.2507.15003 · cited 4×
“Prior work has examined how developers interact with AI-generated code and the impact of these tools on productivity and software quality [34, 37, 38, 50, 51].”
InfluentialTowards AI-Native Software Engineering (SE 3.0): A Vision and a Challenge Roadmap
Hassan, A. E., Oliva, G. A., Lin, D., et al. (2024) · arXiv · doi:10.48550/arxiv.2410.06107
How AI Coding Agents Modify Code: A Large-Scale Study of GitHub Pull Requests
Ogenrwot, D., & Businge, J. (2026) · arXiv · doi:10.48550/arxiv.2601.17581
Self-citationPatchTrack: A Comprehensive Analysis of ChatGPT's Influence on Pull Request Outcomes
Ogenrwot, D., & Businge, J. (2025) · arXiv · doi:10.48550/arxiv.2505.07700
Self-citationConflictbench: A Benchmark to Evaluate Software Merge Tools
Shen, B., & Meng, N. (2023) · doi:10.2139/ssrn.4529909
Untitled work
(n.d.) · doi:10.1007/s10664-
UnresolvedUntitled work
(n.d.) · doi:10.1109/scam67354
UnresolvedUntitled work
(n.d.) · doi:10.1007/978-3-
UnresolvedUntitled work
(n.d.) · doi:10.1109/tse.2021
UnresolvedJohn Businge, Alexandre Decan, Ahmed Zerouali, Tom Mens, and Serge Demeyer. 2020. An Empirical Investigation of Forks as Variants in the npm Package Distribution. In Proceedings of the 19th Belgium-Netherlands Software Evolution Workshop, BENEVOL 2020, Luxembourg, December 3-4, 2020 (CEUR Workshop P
John, B. (2020)
UnresolvedCursor. 2025. Cursor: AI Code Editor. https://cursor.com/. Accessed: 2025-12-14.
(2025)
UnresolvedDevin AI. 2025. Devin AI -AI Coding Assistant. https://app.devin.ai/. Accessed: 2025-12-14.
(n.d.)
UnresolvedRoberto Di Cosmo and Stefano Zacchiroli. 2017. Software heritage: Why and how to preserve software source code. In iPRES 2017.
Di, C. R. (2017)
UnresolvedGit Project. 2026. Partial Clone. https://git-scm.com/docs/partial-clone. Accessed: 2026-04-02.
(n.d.)
UnresolvedGitHub Copilot. 2025. GitHub Copilot. https://github.com/copilot. Accessed: 2025-12-14.
(n.d.)
UnresolvedGitHub Inc. 2026. GitHub Terms of Service. https://docs.github.com/en/sitepolicy/github-terms/github-terms-of-service. Accessed: 2026-04-02.
(n.d.)
UnresolvedGitHub Inc. 2026. GraphQL API. https://docs.github.com/en/graphql. Accessed: 2026-04-02.
(n.d.)
UnresolvedGitHub Inc. 2026. Rate limits and query limits for the GraphQL API. https://docs.github.com/en/graphql/overview/rate-limits-and-query-limitsfor-the-graphql-api. Accessed: 2026-04-02.
(n.d.)
UnresolvedKosei Horikawa, Hao Li, Yutaro Kashiwa, Bram Adams, Hajimu Iida, and Ahmed E Hassan. 2025. Agentic Refactoring: An Empirical Study of AI Coding Agents. arXiv preprint arXiv:2511.04824 (2025).
Kosei, H. (2025)
UnresolvedHao Li, Haoxiang Zhang, and Ahmed E. Hassan. 2025. The Rise of AI Teammates in Software Engineering (SE) 3.0: How Autonomous Coding Agents Are Reshaping Software Engineering. arXiv preprint arXiv:2507.15003 (2025).
Hao, L. (2025)
UnresolvedOpenAI. 2025. Codex -OpenAI. https://openai.com/codex/. Accessed: 2025-12- 14.
(n.d.)
UnresolvedPriyan Vaithilingam, Zheng Xu, and Elena L. Glassman. 2023. Copilot or Co- Author? Examining the Role of Code Generation Tools in Collaborative Programming. In Proceedings of the 2023 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC). IEEE, USA.
Priyan, V. (n.d.)
UnresolvedPriyan Vaithilingam, Tianyi Zhang, and Elena L. Glassman. 2022. Expectation vs. Experience: Evaluating the Usability of Code Generation Tools Powered by Large Language Models. In Proceedings of the 2022 CHI Conference on Human Factors in Computing Systems. ACM, USA, 1-17.
Priyan, V. (n.d.)
UnresolvedMiku Watanabe, Hao Li, Yutaro Kashiwa, Brittany Reid, Hajimu Iida, and Ahmed E. Hassan. 2025. On the Use of Agentic Coding: An Empirical Study of Pull Requests on GitHub. arXiv:2509.14745 [cs.SE] https://arxiv.org/abs/2509.14745
Miku, W. (2025)
Unresolved
Cited by
ATM: CID-Brokered Pre-Write Admission for Multi-Agent Code Co-Synthesis
Huang, E. (2026) · arXiv · doi:10.48550/arxiv.2607.00041
EA-Graph: Artifact-Anchored Verification Memory for Coding Agents under Upstream DriftPreprint
Hsu, H.-J., Chi, C.-J., & Everett, H. (2026) · arXiv (Cornell University) · doi:10.48550/arxiv.2608.04278 · Cited by 2
“Examples include admission control before writes [12], process-aware conflict detection [13], and a large-scale study of merge conflicts in agent-authored pull requests [14].”
Subramanian, A., Xu, G., & Karthik, N. (2026) · arXiv (Cornell University) · doi:10.48550/arxiv.2610.04779
“AIDev provides a large observational substrate for coding-agent activity [2]; AgenticFlict measures conflicts involving agent-authored PRs [3]; SWE-bench evaluates isolated issue resolution against executable tests [12].”
Passes Alone, Fails Together: Benchmarking Semantic Coordination in Parallel LLM-Agent Development
Xia, H., Wu, E., & Park, Y. (2026) · Proceedings of the 2nd Workshop on Explainable and Reliable Software Systems · doi:10.1145/3842650.3843171
Govern the Repository, Not the Agent: Measuring Ecosystem-Level Risk in AI-Native SoftwarePreprint
Russo, D. (2026) · arXiv.org · doi:10.48550/arxiv.2606.28235
“…datasets record agent-authored pull requests at scale [1], [2], AgenticFlict records whether each pull request would conflict with its evolving base branch [40], and longitudinal industry analysis links rising AI-assisted development to more duplicated code and churn and less refactoring [41].”
Metadata
- Authors
- Ogenrwot, D., & Businge, J.
- Affiliations
- University of Nevada, Las Vegas (US)
- Venue
- Proceedings of the 3rd ACM International Conference on AI-Powered Software
- Publisher
- ACM
- Published
- 2026-07-05
- Pages
- 323-331
- OpenAlex
- W7161290748
- Cited by
- 0
- References
- 58
- FWCI
- 0.00
- Type
- conference paper
- Language
- en
- Open access
- hybrid
- doi.org
- Locations
- ACM International Conference on AI-Powered Software (AIware) (publishedVersion, cc-by)
- arXiv (Cornell University) (submittedVersion, cc-by)
- arXiv (Cornell University) (cc-by)
- Funders
- National Science Foundation (2519136, 2117941)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
- Keywords
- merge conflicts, coding agents, pull requests, GitHub, AI-assisted software development, conflict zones, collaborative software development
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.
The claim verdicts this report counts are experimental: their accuracy is not yet measured.
A language model drew the claims from the paper on 2026-10-10, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).
A second model labelled each claim on 2026-10-10 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).
Cited sources are checked with a language model’s help (gpt-6-sol and qwen3.8-omni-flash).
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
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.