How GitHub Uses Rails

This article discusses advanced methods of creating Preset annotations for design system components, focusing on how to enhance accessibility and usability.

The article discusses how GitHub's Product Security Engineering team utilizes CodeQL, a static analysis engine, to enhance the security of GitHub's codebase.

The article discusses how GitHub improved system availability through iterative simplification, focusing on the tools and methods used to address performance issues.

The article discusses improvements made to GitHub's push processing system, which previously relied on a single, complex background job.

The article discusses GitHub's successful deployment of Rails 6. 0, highlighting the significant contributions made by GitHub engineers and the smooth upgrade process.

The article discusses the optimization introduced in Ruby 2. 6, specifically focusing on direct instruction marking, which reduces memory usage by eliminating the need for a mark array.

GitHub successfully upgraded its main application from Rails 3.2 to 5.2.1 over a year and a half, addressing technical debt and improving the codebase while maintaining ongoing feature development.

GitHub has successfully removed jQuery from its frontend code, marking a significant transition towards using standard browser APIs.

The article discusses how GitHub mitigates replication lag and reduces read load on MySQL databases using a service called Freno.

The article discusses GitHub's transition of its Ruby on Rails application infrastructure to Kubernetes, detailing the challenges faced and the lessons learned throughout the migration process.

This article discusses GitHub's evolution in implementing Content Security Policy (CSP) and the subsequent measures taken to defend against post-CSP exploitation.

The article discusses Spokes, GitHub's replication system for file servers, emphasizing its resilience through durability and availability.

GitHub has transitioned from using icon fonts to SVGs for delivering Octicons across its platform.

GitHub's Metal Cloud emphasizes stability, availability, and performance by deploying services on bare-metal hardware.

This article details GitHub's deployment process, emphasizing the use of pull request branches and the importance of continuous integration.

The article discusses how GitHub utilizes its own platform to document its services effectively.

The article discusses the migration of GitHub Pages to their own domain, aimed at mitigating phishing attacks and cross-domain cookie vulnerabilities.