将主要的 Zig 仓库从 GitHub 迁移到 Codeberg
Migrating the Main Zig Repository from GitHub to Codeberg

原始链接: https://ziglang.org/news/migrating-from-github-to-codeberg/

## Zig 项目从 GitHub 迁移至 Codeberg 经过十年,Zig 编程语言由于微软收购后日益出现的问题,将离开 GitHub。该项目指出,平台质量下降——性能迟缓、CI 系统(GitHub Actions)被忽视以及不想要的 AI 集成——是迁移的关键原因。对 GitHub 发展方向的担忧以及关键人员的离职,例如倡导 GitHub Sponsors 的 Devon Zuegel,进一步促成了这一决定。 虽然 GitHub Sponsors 目前提供了重要的资金支持,但 Zig 软件基金会认为它越来越不可靠。他们请求支持者将捐款迁移至非营利组织 Every.org,并正在努力在新平台上复制现有的捐款福利。 主要的 Zig 仓库现在在 GitHub 上为只读状态,并在 Codeberg.org 上进行了镜像。现有的 GitHub issue 和 pull request 将保持开放,但被视为“写时复制”,这意味着除非需要进一步操作,否则无需迁移。此举代表着对独立性的承诺,以及面对平台整合时对开源价值的维护。

## Zig 语言从 GitHub 迁移至 Codeberg Zig 编程语言已将其主仓库从 GitHub 迁移至 Codeberg,GitHub 仓库现为只读状态。此举源于多种因素,包括减少 AI 生成的问题垃圾信息(特别是来自 GitHub Copilot 的)以及对 GitHub 平台发展方向的担忧。 评论者普遍支持这一决定,认为 Codeberg 比 SourceHut 等替代方案更具长期稳定性。一些人赞赏远离 GitHub 的激励结构,该结构鼓励提升个人资料的活动。 虽然缺乏镜像的 GitHub 仓库让一些人担忧,但许多人认为这是朝着多样化开源托管和支持与项目价值观相符的平台迈出的积极一步。Zig 团队也表示他们将为 Codeberg 的服务提供资金支持。
相关文章

原文
← Back to News page

November 26, 2025

Ever since git init ten years ago, Zig has been hosted on GitHub. Unfortunately, when it sold out to Microsoft, the clock started ticking. “Please just give me 5 years before everything goes to shit,” 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 folks who used to work on the product have moved on to bigger and better things, with the remaining losers eager to inflict some kind of bloated, buggy JavaScript framework on us in the name of progress. Stuff that used to be snappy is now sluggish and often entirely broken.

More importantly, Actions is created by monkeys and completely neglected. After the CEO of GitHub said to “embrace AI or get out”, it seems the lackeys at Microsoft took the hint, because GitHub Actions started “vibe-scheduling”; choosing jobs to run seemingly at random. Combined with other bugs and inability to manually intervene, this causes our CI system to get so backed up that not even master branch commits get checked.

Rather than wasting donation money on more CI hardware to work around this crumbling infrastructure, we’ve opted to switch Git hosting providers instead.

As a bonus, we look forward to fewer violations (exhibit A, B, C) of our strict no LLM / no AI policy, which I believe are at least in part due to GitHub aggressively pushing the “file an issue with Copilot” feature in everyone’s face.

GitHub Sponsors

The only concern we have in leaving GitHub behind has to do with GitHub Sponsors. This product was key to Zig’s early fundraising success, and it remains 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 into a viable source of income for thousands of developers. Under her leadership, the future of GitHub Sponsors looked bright, but sadly for us, she, too, moved on to bigger and better things. Since she left, that product as well has been neglected and is already starting to decline.

Although GitHub Sponsors is a large fraction of Zig Software Foundation’s donation income, we consider it a liability. We humbly ask if you, reader, are currently donating through GitHub Sponsors, that you consider moving your recurring donation to Every.org, which is itself a non-profit organization.

As part of this, we are sunsetting the GitHub Sponsors perks. These perks are things like getting your name onto the home page, and getting your name into the release notes, based on how much you donate monthly. We are working with the folks at Every.org so that we can offer the equivalent perks through that platform.

Migration Plan

Effective immediately, I have made ziglang/zig on GitHub read-only, and the canonical origin/master branch of the main Zig project repository is https://codeberg.org/ziglang/zig.git.

Thank you to the Forgejo contributors who helped us with our issues switching to the platform, as well as the Codeberg folks who worked with us on the migration - in particular Earl Warren, Otto, Gusted, and Mathieu Fenniak.

In the end, we opted for a simple strategy, sidestepping GitHub’s aggressive vendor lock-in: leave the existing issues open and unmigrated, but start counting issues at 30000 on Codeberg so that all issue numbers remain unambiguous. Let us please consider the GitHub issues that remain open as metaphorically “copy-on-write”. Please leave all your existing GitHub issues and pull requests alone. No need to move your stuff over to Codeberg unless you need to make edits, additional comments, or rebase. We’re still going to look at the already open pull requests and issues; don’t worry.


In this modern era of acquisitions, weak antitrust regulations, and platform capitalism leading to extreme concentrations of wealth, non-profits remain a bastion defending what remains of the commons.

Happy hacking,

Andrew

联系我们 contact @ memedata.com