GitHub Copilot Blog

7 stories

GitHub Copilot BlogToolsSecret protection must scale with software Today, one in three pull requests on GitHub involves an AI agent . A year ago, that number was fewer than one in 10.

10.07

GitHub Copilot BlogToolsReviewBench: An open benchmark for AI code review Agentic code review is becoming an essential piece of how development happens. It helps you inspect pull requests, catch issues, and decide what deserves attention before code ships.

10.05

GitHub Copilot BlogToolsGitHub Copilot app for Beginners: How to build custom workflows with canvases Most tools give you a fixed set of screens and ask you to fit your work into them. But what if you could start with the workflow you want instead and have the interface take shape around it?

09.25

GitHub Copilot BlogToolsWhen chat is the wrong UI We’re 176 years into this AI experiment. Wait…it’s only been three years? Are you sure? Sometimes I remember things that happened last year, but it feels like it was so long ago.

09.24

GitHub Copilot BlogToolsRendering huge pull requests in the GitHub Copilot app Broad refactors and migrations often have to land as one change. Stacked pull requests are a great way to split work into smaller changes, which makes reviews easier and helps teams ship with less…

09.23

GitHub Copilot BlogToolsMigrating the GitHub Copilot runtime to Rust, using Copilot The GitHub Copilot CLI , GitHub Copilot app , and GitHub Copilot SDK are all backed by the Copilot agent runtime, an agentic harness that can be embedded into applications and services.

09.17

GitHub Copilot BlogToolsMarketing ops as code: Automating events from planning to follow-up on GitHub I run marketing for GitHub in Japan and Korea, and events are the heartbeat of it: a recurring webinar series for enterprise developers, community meetups in Tokyo, invite-only executive sessions in…

09.11

The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo