Long-term GitHub users have grown increasingly frustrated by its struggle to cope with exponential growth in pull requests, automation and monorepos driven by developers adopting coding agents, which in turn has exposed
with the scale at which the service now runs. __architectural decisions that haven’t kept up__When former HashiCorp co-founder Mitchell Hashimoto announced in April he was moving his open source
[project off GitHub and would probably use](https://github.com/ghostty-org/ghostty?ref=thestack.technology)
__Ghostty terminal__[(which he called “awesome”) for CI/CD, there was](https://buildkite.com/home/?ref=thestack.technology)
an unusual outpouring of enthusiasm## Dynamic and developer centric
Buildkite started as a personal project; the original founder wanted a developer experience more like Heroku than Jenkins. Much of the original focus was about giving developers more control over software delivery, down to CI/CD pipelines and testing. That didn't stop platform teams at larger organisations like Shopify and PagerDuty from picking up Buildkite, often as an internal standard to replace multiple CI/CD systems chosen by individual teams.
Get the full story: Subscribe for free #
Join peers managing over $100 billion in annual IT spend and subscribe to unlock full access to The Stack’s analysis and events.
[Subscribe now](https://www.thestack.technology/membership/)
Already a member? [Sign in](https://www.thestack.technology/signin/)