← Back
news
page
26 November 2025
since git init Ten years ago, Zig was hosted on GitHub. Unfortunately, when it was sold to Microsoft, the clock started ticking. “Please give me 5 years before everything goes to waste,” I thought to myself. And here we are, 7 years later, living on borrowed time.
Putting aside GitHub’s relationship with ICE, it’s abundantly clear that the talented people who used to work on the product have moved on to bigger and better things, leaving the remaining losers eager to foist some kind of bloated, poor JavaScript framework on us in the name of progress. Stuff that used to be fast has now become sluggish and often breaks completely.
More importantly, the verbs are created by monkeys and are completely ignored. After GitHub’s CEO said to “embrace AI or opt out”, it seems the bastards at Microsoft got the hint, as GitHub Actions started “vibe-scheduling”; Randomly selecting jobs to run. Combined with other bugs and the inability to manually intervene, this causes our CI system to become so backed up that it can’t even check master branch commits.
Rather than waste donated money on more CI hardware to work around this crumbling infrastructure, we have opted to change Git hosting providers.
As a bonus, we anticipate fewer violations of our strict no LLM/no AI policy (Exhibit A, B, C), which I believe is at least partially due to GitHub aggressively pushing the “File an issue with Copilot” feature before everyone else.
GitHub Sponsor
Our only concern in leaving GitHub behind is with GitHub sponsors. This product was key to Zig’s early fundraising success, and it continues to be a large portion of our revenue today. I can’t thank Devon Zuegel enough. She appeared like an angel from heaven and single-handedly made GitHub a viable source of income for thousands of developers. Under her leadership, the future of GitHub Sponsors looked bright, but sadly for us, she also moved on to bigger and better things. Since his departure, that product has also been neglected and has already begun to decline.
Although GitHub sponsors a large portion of the Zig Software Foundation’s donation income, We consider it an obligationWe politely ask that if you, the reader, are currently donating through GitHub Sponsors, you consider transferring your recurring donation to Every,org, itself a non-profit organization,
As part of this, we’re eliminating GitHub sponsor allowances. These features are things like registering your name on the home page, and including your name in release notes based on how much you donate monthly. We’re working with the folks at Every.org so we can provide similar features through that platform.
migration plan
Effective immediately, I have made ziglang/zig read-only on GitHub, and the canonical root/master branch of the main Zig project repository https://codeberg.org/ziglang/zig.git,
Thanks to the Forgejo contributors who helped us with our issues switching platforms, as well as the folks at Codeberg who worked with us on the migration – especially Earl Warren, Otto, Gusted, and Matthew Feniak.
In the end, we opted for a simple strategy bypassing GitHub’s aggressive vendor lock-in: leave existing issues open and immigrated, but start the issue count on Codeberg at 30000 so that the number of all issues remains clear. Let’s please consider GitHub issues that remain open as metaphorically “copy-on-write”. Please leave all your existing GitHub issues and pull requests aloneThere’s no need to move your stuff to Codeberg unless you need edits, additional comments, or rebase, We will still see previously open pull requests and issuesDon’t worry.
In this modern age of takeovers, weak antitrust regulations, and platform capitalism leading to extreme concentrations of wealth, the nonprofit remains a bastion protecting what remains of the common people.
Happy hacking,
andrew
<a href