| A Study on the Interplay between Pull Request Review and Continuous Integration Builds
|
2019 |
SANER |
Evaluation, Survey, |
Understanding, |
| Confusion in Code Reviews: Reasons, Impacts, and Coping Strategies
|
2019 |
SANER |
Evaluation, Survey, |
Socio-technical effects,
Understanding, |
| Expressions of Sentiments during Code Reviews: Male vs. Female
|
2019 |
SANER |
Evaluation, |
Socio-technical effects,
Understanding, |
| Rebasing in Code Review Considered Harmful: A Large-Scale Empirical Investigation
|
2019 |
SCAM |
Evaluation, |
Potential benefits, |
| Test-Driven Code Review: An Empirical Study
|
2019 |
ICSE |
Validation, |
Understanding, |
| Why Does Code Review Work for Open Source Software Communities?
|
2019 |
ICSE |
Validation, |
Socio-technical effects,
Understanding, |
| CoRA: Decomposing and Describing Tangled Code Changes for Reviewer
|
2019 |
ASE |
Solution, |
Automation, Program comprehension,
Understanding, |
| Automatic Generation of Pull Request Descriptions
|
2019 |
ASE |
Solution, |
Automation, Program comprehension,
Understanding, |
| Aiding Code Change Understanding with Semantic Change Impact Analysis
|
2019 |
ICSME |
Solution, |
Automation, Program comprehension,
Understanding, |
| Style-Analyzer: Fixing Code Style Inconsistencies with Interpretable Unsupervised Algorithms
|
2019 |
MSR |
Solution, |
Automation, Program comprehension,
Potential benefits, |
| The Review Linkage Graph for Code Review Analytics: A Recovery Approach and Empirical Study
|
2019 |
FSE |
Evaluation, |
Socio-technical effects,
Understanding, |
| Predicting Pull Request Completion Time: A Case Study on Large Scale Cloud Services
|
2019 |
FSE |
Evaluation, |
Potential benefits, |
| Who should make decision on this pull request? Analyzing time-decaying relationships and file similarities for integrator prediction
|
2019 |
JSS |
Evaluation, |
Automation,
|
| Why is my code change abandoned?
|
2019 |
IST |
Evaluation, |
Understanding, Potential benefits, |
| An empirical study of sentiments in code reviews
|
2019 |
IST |
Evaluation, |
Socio-technical effects,
|
| The impact of human factors on the participation decision of reviewers in modern code review
|
2019 |
EMSE |
Evaluation, |
Socio-technical effects,
Understanding, |
| Associating working memory capacity and code change ordering with code review performance
|
2019 |
EMSE |
Validation, |
Understanding, |
| Improving the pull requests review process using learning-to-rank algorithms
|
2019 |
EMSE |
Evaluation, |
Automation,
Understanding, |
| How does code style inconsistency affect pull request integration? An exploratory study on 117 GitHub projects
|
2019 |
EMSE |
Evaluation, |
Program comprehension,
Understanding, |
| Whom are you going to call? determinants of @-mentions in Github discussions
|
2019 |
EMSE |
Evaluation, |
Socio-technical effects,
Understanding, |
| Modern Code Review: A Case Study at Google
|
2018 |
ICSE |
Survey, |
Other,
Understanding, Potential benefits, |
| Was My Contribution Fairly Reviewed?: A Framework to Study the Perception of Fairness in Modern Code Reviews
|
2018 |
ICSE |
Survey, |
Socio-technical effects,
Understanding, Communication, |
| Studying Pull Request Merges: A Case Study of Shopify's Active Merchant
|
2018 |
ICSE |
Evaluation, |
Socio-technical effects,
Quality assurance, Understanding, Communication, |
| When Testing Meets Code Review: Why and How Developers Review Tests
|
2018 |
ICSE |
Evaluation, |
Socio-technical effects,
Quality assurance, Understanding, |
| Studying the Impact of Adopting Continuous Integration on the Delivery Time of Pull Requests
|
2018 |
MSR |
Evaluation, |
Other,
Quality assurance, Understanding, |
| What Makes a Code Change Easier to Review: An Empirical Investigation on Code Change Reviewability
|
2018 |
FSE |
Survey, |
Socio-technical effects,
Potential benefits, |
| BLIMP Tracer: Integrating Build Impact Analysis with Code Review
|
2018 |
ICSME |
Solution, |
Automation,
Quality assurance, |
| How do Multiple Pull Requests Change the Same Code: A Study of Competing Pull Requests in GitHub
|
2018 |
ICSME |
Evaluation, |
Socio-technical effects,
Understanding, Communication, |
| How Maintainability Issues of Android Apps Evolve
|
2018 |
ICSME |
Evaluation, |
Other,
Understanding, Potential benefits, |
| An Empirical Study of Design Discussions in Code Review
|
2018 |
ESEM |
Evaluation, |
Automation,
Understanding, |
| what factors inluence the reviewer assignment to pull request?
|
2018 |
IST |
Evaluation, |
Socio-technical effects,
Understanding, Communication, |
| Does reviewer recommendation help developers?
|
2018 |
TSE |
Evaluation, |
Socio-technical effects,
Communication, |
| Early prediction of merged code changes to prioritize reviewing tasks
|
2018 |
EMSE |
Evaluation, Validation, |
Automation, Socio-technical effects,
Potential benefits, |
| Automatic assignment of integrators to pull requests: The importance of selecting appropriate attributes
|
2018 |
JSS |
Evaluation, |
Automation,
Understanding, |
| Using Stack Overflow content to assist in code review
|
2018 |
SPE |
Evaluation, |
Automation,
Potential benefits, |
| Are Fix-Inducing Changes a Moving Target? A Longitudinal Case Study of Just-In-Time Defect Prediction
|
2018 |
TSE |
Evaluation, Validation, |
Program comprehension, Socio-technical effects,
Quality assurance, Understanding, |
| Decoding the Representation of Code in the Brain: An fMRI Study of Code Review and Expertise
|
2017 |
ICSE |
Validation, |
Program comprehension,
Understanding, |
| Predicting Usefulness of Code Review Comments Using Textual Features and Developer Experience
|
2017 |
MSR |
Evaluation, Validation, |
Automation, Socio-technical effects,
Potential benefits, |
| On the Optimal Order of Reading Source Code Changes for Review
|
2017 |
ICSME |
Survey, |
Other,
Understanding, |
| Semantics-assisted code review: An efficient tool chain and a user study
|
2017 |
ASE |
Validation, Solution, |
Automation, Program comprehension,
Potential benefits, |
| Are developers aware of the architectural impact of their changes?
|
2017 |
ASE |
Evaluation, |
Program comprehension,
Understanding, |
| Can automated pull requests encourage software developers to upgrade out-of-date dependencies?
|
2017 |
ASE |
Evaluation, Validation, |
Socio-technical effects,
Understanding, |
| On the Influence of Human Factors for Identifying Code Smells: A Multi-Trial Empirical Study
|
2017 |
ESEM |
Evaluation, |
Program comprehension, Socio-technical effects,
Potential benefits, |
| How Developers Document Pull Requests with External References
|
2017 |
ICPC |
Evaluation, |
Understanding, Communication, |
| Broadcast vs. Unicast Review Technology: Does It Matter?
|
2017 |
ICST |
Evaluation, Survey, |
Communication, Understanding, |
| Understanding inactive yet available assignees in GitHub
|
2017 |
IST |
Evaluation, |
Socio-technical effects,
Understanding, |
| Who should comment on this pull request? Analyzing attributes for more accurate commenter recommendation in pull-based development
|
2017 |
IST |
Evaluation, Validation, |
Automation, Socio-technical effects,
Potential benefits, |
| Code Reviewing in the Trenches: Challenges and Best Practices
|
2017 |
IEEE Software |
Survey, |
Understanding, Potential benefits, |
| Comparing pre-commit reviews and post-commit reviews using process simulation
|
2017 |
SMR |
Evaluation, |
Understanding, |
| Review participation in modern code review
|
2017 |
EMSE |
Evaluation, Validation, |
Socio-technical effects,
Understanding, |
| Revisiting Code Ownership and Its Relationship with Software Quality in the Scope of Modern Code Review
|
2016 |
ICSE |
Evaluation, Validation, |
Socio-technical effects,
Quality assurance, Understanding, Communication, |
| Work Practices and Challenges in Pull-based Development: The Integrator's Perspective
|
2016 |
ICSE |
Survey, |
Other,
Understanding, Potential benefits, |
| Teaching Code Review Management Using Branch Based Workflows
|
2016 |
ICSE |
Survey, |
Program comprehension,
Quality assurance, Understanding, Potential benefits, |
| Code Review Quality: How Developers See It
|
2016 |
ICSE |
Survey, |
Other,
Quality assurance, Understanding, |
| A Study of the Quality-impacting Practices of Modern Code Review at Sony Mobile
|
2016 |
ICSE |
Evaluation, Solution, Experience, |
Program comprehension,
Quality assurance, |
| CoRReCT: Code Reviewer Recommendation in GitHub Based on Cross-project and Technology Experience
|
2016 |
ICSE |
Validation, Solution, |
Automation, Socio-technical effects,
Potential benefits, |
| Search-Based Peer Reviewers Recommendation in Modern Code Review
|
2016 |
ICSME |
Validation, |
Automation, Socio-technical effects,
Potential benefits, |
| Why are Commits Being Reverted?: A Comparative Study of Industrial and Open Source Projects
|
2016 |
ICSME |
Evaluation, |
Socio-technical effects,
Understanding, Communication, |
| Effectiveness of code contribution: from patch-based to pull-request-based tools
|
2016 |
FSE |
Evaluation, |
Socio-technical effects,
Understanding, Communication, |
| Factors influencing code review processes in industry
|
2016 |
FSE |
Survey, |
Other,
Understanding, |
| Automatically recommending code reviewers based on their expertise: An empirical comparison
|
2016 |
ASE |
Validation, |
Automation,
Potential benefits, |
| Predicting Defectiveness of Software Patches
|
2016 |
ESEM |
Evaluation, |
Automation,
|
| The Impact of Human Discussions on Just-in-Time Quality assurance: An Empirical Study on OpenStack and Eclipse
|
2016 |
SANER |
Evaluation, |
Quality assurance, Potential benefits, |
| A Security Perspective on Code Review: The Case of Chromium
|
2016 |
SCAM |
Evaluation, |
Potential benefits, |
| Reviewer recommendation for pull-requests in GitHub: What can we learn from code review and bug assignment?
|
2016 |
IST |
Evaluation, Validation, |
Automation, Socio-technical effects,
Understanding, Potential benefits, |
| Investigating technical and non-technical factors influencing modern code review
|
2016 |
EMSE |
Evaluation, |
Socio-technical effects, Socio-technical effects,
Understanding, Potential benefits, |
| An empirical study of the impact of modern code review practices on software quality
|
2016 |
EMSE |
Evaluation, Validation, |
Program comprehension, Socio-technical effects,
Quality assurance, Understanding, Potential benefits, |
| Process Aspects and Social Dynamics of Contemporary Code Review: Insights from Open Source Development and Industrial Practice at Microsoft
|
2016 |
TSE |
Survey, |
Socio-technical effects, Other,
Understanding, Communication, |
| Automatically Recommending Peer Reviewers in Modern Code Review
|
2016 |
TSE |
Validation, |
Automation,
Potential benefits, |
| Interactive Code Review for Systematic Changes
|
2015 |
ICSE |
Validation, Solution, |
Automation, Program comprehension,
Potential benefits, |
| Work Practices and Challenges in Pull-based Development: The contributor's Perspective
|
2015 |
ICSE |
Survey, |
Other,
Understanding, Potential benefits, |
| Helping Developers Help Themselves: Automatic Decomposition of Code Review Changesets
|
2015 |
ICSE |
Validation, Solution, |
Automation, Program comprehension,
Potential benefits, |
| Will they like this? Evaluating code contributions with language models
|
2015 |
MSR |
Evaluation, |
Program comprehension, Socio-technical effects,
Understanding, |
| Investigating Code Review Practices in Defective Files: An Empirical Study of the Qt System
|
2015 |
MSR |
Evaluation, Validation, |
Socio-technical effects, Socio-technical effects,
Quality assurance, Understanding, |
| Characteristics of Useful Code Reviews: An Empirical Study at Microsoft
|
2015 |
MSR |
Evaluation, Solution, Experience, |
Socio-technical effects,
Understanding, |
| Lessons Learned from Building and Deploying a Code Review Analytics Platform
|
2015 |
MSR |
Survey, |
Other,
Understanding, |
| Partitioning Composite Code Changes to Facilitate Code Review
|
2015 |
MSR |
Evaluation, |
Automation, Program comprehension,
Potential benefits, |
| Investigating code review quality: Do people and participation matter?
|
2015 |
ICSME |
Evaluation, |
Socio-technical effects,
Quality assurance, Understanding, |
| Who should review this change?: Putting text and file location analyses together for more accurate recommendations
|
2015 |
ICSME |
Evaluation, Validation, |
Automation, Socio-technical effects,
Potential benefits, |
| Four eyes are better than two: On the impact of code reviews on software quality
|
2015 |
ICSME |
Evaluation, |
Program comprehension,
Quality assurance, Understanding, |
| Code review: Veni, ViDI, vic
|
2015 |
SANER |
Solution, |
Program comprehension,
Quality assurance, |
| Do code review practices impact design quality? A case study of the Qt, VTK, and ITK projects
|
2015 |
SANER |
Evaluation, |
Socio-technical effects,
Understanding, |
| Who should review my code? A file location-based code-reviewer recommendation approach for Modern Code Review
|
2015 |
SANER |
Evaluation, |
Socio-technical effects,
Communication, |
| Would static analysis tools help developers with code reviews?
|
2015 |
SANER |
Evaluation, |
Program comprehension,
Understanding, |
| Comparative case studies of open source software peer review practices
|
2015 |
IST |
Evaluation, |
Socio-technical effects,
Understanding, Communication, |
| Using Learning Styles of Software Professionals to Improve Their Inspection Team Performance.
|
2015 |
IJSEKE |
Evaluation, |
Socio-technical effects,
Understanding, |
| An Exploratory Study of the Pull-based Software Development Model
|
2014 |
ICSE |
Evaluation, |
Socio-technical effects,
Understanding, |
| Influence of social and technical factors for evaluating contribution in GitHub (from snowball)
|
2014 |
ICSE |
Evaluation, |
Socio-technical effects,
Understanding, |
| Process Mining Multiple Repositories for Software Defect Resolution from Control and Organization Perspective
|
2014 |
ICSE |
Evaluation, |
Other,
Understanding, Potential benefits, |
| The impact of code review coverage and code review participation on software quality: a case study of the qt, VTK, and ITK projects
|
2014 |
MSR |
Evaluation, Validation, |
Socio-technical effects,
Quality assurance, Understanding, |
| Modern code reviews in open-source projects: which problems do they fix?
|
2014 |
MSR |
Evaluation, |
Socio-technical effects,
Understanding, |
| Learning natural coding conventions
|
2014 |
FSE |
Validation, Solution, |
Automation, Program comprehension,
Potential benefits, |
| Identifying the characteristics of vulnerable code changes: an empirical study
|
2014 |
FSE |
Evaluation, |
Automation,
Quality assurance, Potential benefits, |
| Let's talk about it: evaluating contributions through discussion in Github
|
2014 |
FSE |
Evaluation, |
Socio-technical effects,
Communication, |
| Impact of developer reputation on code review outcomes in OSS projects: an empirical investigation
|
2014 |
ESEM |
Evaluation, |
Socio-technical effects,
Understanding, |
| Peer Review on Open-Source Software Projects: Parameters, Statistical Models, and Theory
|
2014 |
TOSEM |
Evaluation, |
Socio-technical effects,
Understanding, Potential benefits, |
| Expectations, Outcomes, and Challenges of Modern Code Review
|
2013 |
ICSE |
Survey, |
Other,
Understanding, Potential benefits, |
| Reducing Human Effort and Improving Quality in Peer Code Reviews Using Automatic Static Analysis and Reviewer Recommendation
|
2013 |
ICSE |
Validation, |
Automation,
Quality assurance, Potential benefits, |
|
Will my patch make it? And how fast? Case study on the Linux kernel
|
2013 |
MSR |
Evaluation, |
Socio-technical effects,
Understanding, |
| Writing acceptable patches: An empirical study of open source project patches
|
2013 |
ICSME |
Evaluation, |
Other,
Understanding, |
| Convergent contemporary software peer review practices
|
2013 |
FSE |
Evaluation, |
Socio-technical effects,
Understanding, Potential benefits, |
| Impact of Peer Code Review on Peer Impression Formation: A Survey
|
2013 |
ESEM |
|
Socio-technical effects,
Understanding, |
| The influence of non-technical factors on code review
|
2013 |
WCRE |
Evaluation, |
Socio-technical effects,
Understanding, |
| A large-scale empirical study of just-in-time quality assurance
|
2013 |
TSE |
Evaluation, Validation, |
Socio-technical effects,
Quality assurance, Potential benefits, |
| How do software engineers understand code changes?: an exploratory study in industry
|
2012 |
FSE |
Survey, |
Program comprehension,
Understanding, |
| Do crosscutting concerns cause modularity problems?
|
2012 |
FSE |
Evaluation, |
Program comprehension,
Understanding, |
| The Secret Life of Patches: A Firefox Case Study
|
2012 |
WCRE |
Validation, |
Socio-technical effects,
Potential benefits, |
| Comparing the Defect Reduction Benefits of Code Inspection and Test-Driven Development
|
2012 |
TSE |
Validation, |
Program comprehension, Other,
Quality assurance, |
| Contemporary Peer Review in Action: Lessons from Open Source Development
|
2012 |
IEEE Software |
Experience, |
Potential benefits, |
| Fully employing software inspections data
|
2012 |
ISSE |
Experience, |
Understanding, Potential benefits, |
| Understanding Broadcast Based Peer Review on Open Source Software Projects
|
2011 |
ICSE |
Evaluation, |
Socio-technical effects,
Understanding, Communication, |
| ICMM - a maturity model for software inspections
|
2011 |
SMR |
Validation, |
Potential benefits, |