Github engineering

Think about the last big feature you shipped. Be honest. Did you cram it into one giant pull request, or

Suppose a user searches for café and your corpus contains CAFÉ, or they type straße and you’ve stored STRASSE. To

If you maintain an active repository, you know the feeling. You open your notifications on a Monday morning and there

The most expensive part of a small feature request used to be writing the code. Now it’s usually the meeting

Give an agent better tools and it should do better work. That’s the instinct, anyway. When you open a pull

“Where are the docs?” It’s a question nobody on a product team enjoys answering. The honest reply is usually some

When you’re working through a backlog—opening an issue, jumping to a linked thread, then back to the list—latency isn’t just

Did you know that, at GitHub, we host all of our own source code on github.com? We do this because

Pull requests are the beating heart of GitHub. As engineers, this is where we spend a good portion of our

I may have just automated myself into a completely different job… This is a familiar pattern among software engineers, who