A bold move: Zig's departure from GitHub sparks debate.
In a surprising turn of events, the Zig programming language development team has decided to part ways with GitHub, a move that has left many in the tech community intrigued. Let's dive into the reasons behind this decision and explore the implications.
The Zig team, after a decade on GitHub, has chosen to relocate its central repository to Codeberg, a non-profit Git hosting service. But here's where it gets controversial: the decision wasn't solely based on personal preference.
According to Zig's project leader, Andrew Kelly, the move was prompted by persistent technical issues, particularly within GitHub Actions. One notable example is the bug in the safe_sleep.sh script, which, under specific conditions, consumed 100% of the CPU and refused to stop. This issue, reported in April 2025, remained unresolved until December 2025, despite the fix being available in August.
The Register sheds light on the bug's origin, tracing it back to a 2022 change where the POSIX command sleep was replaced by the script safe_sleep. Under heavy load, this script could hang, rendering runners unusable until manual intervention.
Zig highlights that such problems were becoming more frequent in GitHub Actions, with the platform's unpredictable task scheduling exacerbating the issue. Combined with limited intervention options, this led to a CI chain that frequently crashed. Zig's foundation opted against investing in additional hardware to mitigate these delays.
But that's not all. Zig's Software Foundation has a strict policy against the use of LLMs and generative AI. As GitHub increasingly integrates AI components into its platform, Zig foresees potential undesirable interactions. By migrating to Codeberg, the foundation aims to create an environment that aligns with its policy.
The switch also impacts Zig's financial structure. GitHub Sponsors, a significant income source for the Zig Software Foundation for years, is now considered a risky dependency. The organization is urging donors to transfer their recurring contributions to Every.org, another non-profit. Existing sponsor benefits within GitHub will be phased out and made available through Every.org.
The migration to Codeberg is now complete. The GitHub repository is in read-only mode, and the official source for Zig's code has moved. Existing issues and pull requests will remain on GitHub, while new issues will start on Codeberg from number 30000 to avoid confusion. Developers will continue to address open items on GitHub.
Codeberg's growth is evident, with its supporting member count doubling since the year's start, now surpassing 1,200.
With this move, Zig aims to establish a more stable and predictable development environment, free from GitHub's technical choices and commercial priorities.
And this is the part most people miss: Zig's decision is a bold statement about the balance between technological advancement and maintaining control over one's development environment. It raises questions about the role of AI in open-source communities and the potential risks of overreliance on certain platforms.
What are your thoughts on Zig's move? Do you think it's a wise decision, or is it a step backward in terms of collaboration and innovation? Feel free to share your opinions in the comments!
