Engineering principles

We’ve always used GitHub to build GitHub. 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.

Featured

Image of a globe with GitHub Enterprise Cloud Data residency overlaying in the title

GitHub Enterprise Cloud with data residency: How we built the next evolution of GitHub Enterprise using GitHub

How we used GitHub to build GitHub Enterprise Cloud with data residency.

The ultimate guide to developer happiness

Five actionable tips and strategies to supercharge developer happiness—and a more innovative workplace.

A landscape image with a simple dark background featuring two security-themed shapes in the top left and bottom right corners. The foreground text is centered and reads "Strategies for supporting your neurodivergent employees."

How GitHub supports neurodiverse employees (and how your company can, too)

Teams with neurodivergent employees can be up to 30 percent more productive. Discover tips on how best to support them in your workplace.

How we improved availability through iterative simplification

Solving and staying ahead of problems when scaling up a system of GitHub’s size is a delicate process. Here’s a look at some of the tools in GitHub’s toolbox, and how we’ve used them to solve problems.

Latest

Empowering accessibility: GitHub’s journey building an in-house Champions program

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.

How GitHub uses merge queue to ship hundreds of changes every day

Here’s how merge queue transformed the way GitHub deploys changes to production at scale, so you can do the same for your organization.

Bringing npm registry services to GitHub Codespaces

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.

GitHub’s Engineering Fundamentals program: How we deliver on availability, security, and accessibility

The Fundamentals program has helped us address tech debt, improve reliability, and enhance observability of our engineering systems.

How GitHub’s Developer Experience team improved innerloop development

Our latest solution to the ubiquitous engineering problem of integration testing in a distributed service ecosystem here at GitHub.

How to communicate like a GitHub engineer: our principles, practices, and tools

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.

How we work: inclusive retrospectives for the GitHub Accessibility leadership team

Learn about tools and processes the GitHub Accessibility leadership team uses for retrospectives that fully engage every team member.

How the Grafana Alerting team scales their issue management with GitHub Projects

Hear from Grafana Labs’ Armand Grillet about how his team uses GitHub Projects.

Filtered view of a project showing only tasks that have been assigned to the user viewing the list.

How the GitHub Docs team uses GitHub Projects

Explore how the GitHub Docs team uses GitHub Projects for content coordination, reviews, and publishing.

Enabling branch deployments through IssueOps with GitHub Actions

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!