The GitHub Ruby on Rails monolith is big: nearly two million lines of code and more than 1,000 engineers collaborating on it, to the tune of around 20 deployments every day. Follow along to see how we build and continually improve the tools you use every day.
Pushing code to GitHub is one of the most fundamental interactions that developers have with GitHub every day. Read how we have significantly improved the ability of our monolith to correctly and fully process pushes from our users.
Take CODEOWNERS and GitHub teams to the next level. Learn about how GitHub engineering solves the age old problem of who owns what.
Use our new open source Trace2 receiver component and OpenTelemetry to capture and visualize telemetry from your Git commands.
See how much more you can get out of GitHub Codespaces by taking advantage of the improved processing power and increased headroom in the next generation of virtual machines.
Learn about how we build containerized services that power microservices on the GitHub.com platform and many internal tools.
The new GitHub Code View brings users many new features to improve the code reading and exploration experiences, and we overcame a number of unique technical hurdles in order to deliver those features without compromising performance.
Since the beginning, GitHub.com has been a Ruby on Rails monolith. Today, the application is nearly two million lines of code and more than 1,000 engineers collaborate on it daily.…
GitHub Docs recently changed its site-search to Elasticsearch. Here’s how it was implemented.
A look at what went into building the world’s largest public code search index.
The GitHub Actions team has done lots of work to improve the performance and resource consumption of Actions on GHES in the past year.
A tour of recent work to re-engineer Git’s garbage collection process to scale to our largest and most active repositories.
At GitHub we use GitHub to build our own products, and the new projects experience is no different. Check out how our team uses projects to build powerful project planning for developers.
The history of pre-receive hooks, how we discovered that the performance was problematic, and how we went about safely replacing them.
How we sped up GitHub.com by moving slow, non-critical code into rack.after_reply.
This blog post tells the story of why we built a new search engine optimized for code.
Today, we are rolling out a technology preview for GitHub code search, the next iteration for search, discovery, and navigation on GitHub.
At GitHub, we pride ourselves on delivering a first-class developer experience. A considerable part of our work is on our front end, which we strive to keep as lightweight, fast,…
Rendering logs in a web UI might seem simple: they are just lines of plain text. However, there are a lot of additional features that make them more useful to…
GitHub’s mobile applications have used GraphQL to power new features. We’ve now been able to move faster and get more done with less hassle and no over-fetching. We were able…
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.
