We’ve always used GitHub to build GitHub. Thanks to our tools, asynchronous communication has been baked into how we operate from the very beginning. Over the years, we’ve also adopted practices from the open source community for our own internal collaboration needs. Learn more about how we work with a global and diverse team and make informed, inclusive, and scalable decisions.
As part of GitHub’s dedication to accessibility, we expanded our internal accessibility program and scaled up our assessment process to help remove or lower barriers for users with disabilities. Then, we empowered employees from various disciplines to drive accessibility efforts within their teams.
Here’s how merge queue transformed the way GitHub deploys changes to production at scale, so you can do the same for your organization.
The npm engineering team recently transitioned to using GitHub Codespaces for local development for npm registry services. This shift to Codespaces has substantially reduced the friction of our inner development loop and boosted developer productivity.
The Fundamentals program has helped us address tech debt, improve reliability, and enhance observability of our engineering systems.
Our latest solution to the ubiquitous engineering problem of integration testing in a distributed service ecosystem here at GitHub.
Learn more about how we use GitHub to build GitHub, how we turned our guiding communications principles into prescriptive practices to manage our internal communications signal-to-noise ratio, and how you can contribute to the ongoing conversation.
Learn about tools and processes the GitHub Accessibility leadership team uses for retrospectives that fully engage every team member.
Hear from Grafana Labs’ Armand Grillet about how his team uses GitHub Projects.
Explore how the GitHub Docs team uses GitHub Projects for content coordination, reviews, and publishing.
What if developers want to leverage branch deployments but don’t have a full ChatOps stack integrated with their repositories? We wanted to set out to find a way for all developers to be able to take advantage of branch deployments with ease, right from their GitHub repository, and so the branch-deploy Action was born!
When teams work cross-functionally, good things happen. See how our teams use GitHub Projects to coordinate and ship new products and features.
What in the world do rubber ducks have to do with programming? And why were they everywhere at GitHub Universe? A lot of you asked, so I’m here to help explain.
Our engineering and security teams do some incredible work. Let’s take a look at how we use GitHub to be more productive, build collaboratively, and shift security left.
Can projects and GitHub Actions be used by your non-developer teams? They absolutely can. Check out how our Security Team uses GitHub to run the department effortlessly.
👋 Hello from the GitHub Docs team! We build everything you see at docs.github.com. Over the past year, we’ve written a bunch of GitHub Actions workflows to do some fun…
It has been a year since we’ve launched the first public release of GitHub CLI. Since, we have added functionality to manage your repositories, comment on issues, enable auto-merge for…
GitHub’s engineering group moved from a monolithic, hero-based on-call rotation to a more balanced on-call culture in order to increase our on-call expertise and improve the experience for our customers.
This is the second post in a series about how we built our new homepage. How our globe is built How we collect and use the data behind the globe…
GitHub is where the world builds software. More than 56 million developers around the world build and work together on GitHub. With our new homepage, we wanted to show how…
Build what’s next on GitHub, the place for anyone from anywhere to build anything.
Get tickets to the 10th anniversary of our global developer event on AI, DevEx, and security.
