Continuous integration in a social-coding world: Empirical evidence from GitHub. **Updated version with corrections**

Alexander Serebrenik; Bogdan Vasilescu; Jules Wulms; Mark G. J. van den Brand; Stef van Schuylenburg

Continuous integration in a social-coding world: Empirical evidence from GitHub. Updated version with corrections

Not yet reviewed by Pith; the record is open.

Re-run · record.json Download PDF Read on arXiv ↗

This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.

SPECIMEN: schema-true, not a live event

T0 review · schema-true

One-sentence machine reading of the paper's core claim.

pith:XXXXXXXX · record.json · timestamp

arxiv 1512.01862 v1 pith:H4ZCPG4D submitted 2015-12-06 cs.SE

Bogdan Vasilescu , Stef van Schuylenburg , Jules Wulms , Alexander Serebrenik , Mark G. J. van den Brand This is my paper · ORCID

classification cs.SE

keywords githubmainprojectcontinuousdevelopersintegrationcomingcopies

verification ladder T0 review T1 audit T2 compute T3 formal

0 comments

read the original abstract

Continuous integration is a software engineering practice of frequently merging all developer working copies with a shared main branch, e.g., several times a day. With the advent of GitHub, a platform well known for its "social coding" features that aid collaboration and sharing, and currently the largest code host in the open source world, collaborative software development has never been more prominent. In GitHub development one can distinguish between two types of developer contributions to a project: direct ones, coming from a typically small group of developers with write access to the main project repository, and indirect ones, coming from developers who fork the main repository, update their copies locally, and submit pull requests for review and merger. In this paper we explore how GitHub developers use continuous integration as well as whether the contribution type (direct versus indirect) and different project characteristics (e.g., main programming language, or project age) are associated with the success of the automatic builds.

Discussion (0). Continue with ORCID to comment.

Forward citations

Cited by 1 Pith paper

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score. Full citation record

LLM-Driven CI-CD Workflow Intelligence for Cyber Systems Engineering
cs.SE 2026-07 conditional novelty 5.5 of 10

An LLM pipeline over 75k GitHub CI/CD workflows finds reliability-dominated anti-patterns, language/domain stage differences, and best recommendation quality from few-shot prompting.

Pith tools