We're launching GitHub Actions analytics in Depot. Make informed decisions about your workflows, with performance trends, resource utilization, and optimization recommendations across all GitHub Actions jobs.
Git's fetch operation shows off the best of its design: simple request-response exchanges and packfiles that sync repos efficiently. Here's how it works and why modern development needs more.
Monorepos promise faster development and better visibility across your stack. But they also introduce scaling problems most teams do not see coming. This post breaks down the tradeoffs, the tooling challenges, and when a monorepo actually makes sense.
Building Rust projects in CI can be painfully slow, but with the right optimizations, you can dramatically reduce build times. We tested various techniques on the Zed codebase and achieved a 35% speedup over our already-optimized baseline, cutting build times from 27 minutes to just 16 minutes.
Maintaining forks of rapidly-evolving upstream repositories is a productivity killer. At Depot, we were spending hours each week manually updating ARM64 patches and reviewing dozens of commits just to keep our GitHub Actions runner images in sync. Here's how we used Claude Code to automate the entire process, turning a weekly time sink into a hands-off CI workflow.
We're excited to launch egress filtering for Depot GitHub Actions Runners. This gives you fine-grained control over which external services your runners can talk to so you can tighten security without giving up performance or flexibility..
We at Depot like making shit fast, whether that's Docker image builds, GitHub Actions runners, Bazel caching, Turborepo, or even our own infrastructure. Recently, we've been working to make EC2 instances boot faster.
Depot now supports larger builders for accelerated Docker image builds. You can now choose a Docker image builder with up to 64 CPUs and 128 GB of memory.
