3 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
Zig has migrated its hosting from GitHub to Codeberg due to dissatisfaction with GitHub's performance and policies, especially after Microsoft's acquisition. Concerns over GitHub Actions' reliability and the decline of GitHub Sponsors prompted this decision. The Zig project will maintain open issues on GitHub while starting fresh on Codeberg.
If you do, here's more
Zig has officially migrated from GitHub to Codeberg after spending ten years on the former platform. The decision stems from frustrations with GitHub's declining performance and management since its acquisition by Microsoft. The article highlights ongoing issues with GitHub Actions, which have become unreliable and inefficient. The author points out that instead of investing in more hardware to cope with these problems, Zig opted to switch to a new hosting provider. The move also aligns with their stance against GitHub's promotion of AI tools, which violate their strict no AI policy.
A primary concern for Zig during this transition is GitHub Sponsors, which has been vital for fundraising. The departure of Devon Zuegel, who significantly contributed to the program's success, left Zig uncertain about its future viability. Despite this reliance, the team views GitHub Sponsors as a liability, urging current supporters to redirect their donations to Every.org, a non-profit organization. As part of the migration, Zig is sunsetting GitHub Sponsors perks, such as name recognition on their home page and in release notes, while working to replicate these benefits on the new platform.
The migration plan involves making the GitHub repository read-only while establishing Codeberg as the new canonical source. Existing issues on GitHub will remain open but untransferred to avoid confusion; the issue count will start at 30,000 on Codeberg. The team is grateful for the support received during the transition, particularly from contributors on both platforms, and reassures users that they will continue to monitor existing pull requests and issues.
Questions about this article
No questions yet.