Why Zig Is Moving on From GitHub  ## Metadata - Author: [[Chris Stokel-Walker]] - Full Title: Why Zig Is Moving on From GitHub - Category: #articles - Document Note: --- tags: [GitHub, AI, open-source] author: Chris Stokel-Walker source: LeadDev reference: [https://leaddev.com/ai/why-zig-is-moving-on-from-github] date created: 2025-12-08 12:00 --- # 🏷️ Title: Why Zig is moving on from GitHub ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened. - Zig’s project lead Andrew Kelly decided to move the Zig project off GitHub, criticizing GitHub Actions as “completely neglected” and GitHub’s AI-first direction. - Why it matters. - Highlights growing tension between AI automation and code quality/maintainability on major dev platforms. - Key stakeholders. - Zig community, GitHub/Microsoft, open-source maintainers, AI tooling vendors. - Risks and tradeoffs. - Platform fragmentation, migration costs vs. potential gains in reliability and transparency; unresolved industry-wide issues even if one project leaves. - Bottom line. - Kelly’s move is a protest signal: without focus on reliability, craftsmanship, and maintenance, AI-heavy roadmaps risk eroding developer trust and increasing technical debt. ## 📖 Main Content - Core arguments - Kelly argues GitHub has decayed since the Microsoft acquisition: “engineering excellence” has been replaced by bloat and AI hype. GitHub Actions is described as buggy, unreliable (“vibe-scheduling”), and under-maintained, undermining confidence in automated workflows. - Other experts in the article agree that naive AI deployment can worsen burnout and technical debt by accelerating low-quality code rather than improving quality and maintenance. - Some, like Guillaume Moigneu, see Zig’s move to Codeberg as understandable but argue that the underlying problems (AI misuse, low-quality contributions, platform priorities) are industry-wide and cannot be solved by a single platform switch. - Context and definitions - GitHub Actions: workflow automation to build/test/deploy code on events such as pushes or PRs. - “Agentic AI”: systems that autonomously propose and sometimes apply code changes in loops. - The article connects Kelly’s critique to a broader debate about whether AI helps or undermines “software craftsmanship” and thoughtful design. - Uncertainties / contested claims - The severity and generality of failures in Actions and “vibe-scheduling” are based on Kelly’s experience; there’s no quantitative reliability data here. - The long-term net effect of AI coding tools on quality and sustainability remains unclear and is actively debated. ### 🗒️ Notes - Zig is a highly regarded programming language (per the 2025 Stack Overflow survey), making this move symbolically important. - Kelly’s blog post (not quoted in full here) contains strong language about post-acquisition decline at GitHub, including a prediction that things would “go to shit” within five years. - He specifically targets GitHub Actions: “inexcusable bugs” and being “completely neglected,” along with erratic scheduling behavior described as “vibe-scheduling” where jobs seem to run at random. - Kelly links this to GitHub leadership’s “embrace AI or get out” message, implying resources have been diverted from core reliability to AI initiatives. - Tom Finch (Chainguard) warns that if AI is only used to speed up code creation without solving maintenance and quality, it will accelerate burnout and technical debt. - The article emphasizes that Zig is not alone in facing a flood of low-quality, AI-generated contributions, complicating open-source maintainers’ work. - Moigneu (Upsun) supports the criticism but doubts that leaving GitHub alone will solve structural issues; industry-wide conventions and safeguards are needed. - Jeremy Howard (Answer.ai / Fast.ai) warns AI can erode “software craftsmanship,” encouraging quick symptom fixes over thoughtful architecture. - Howard gives an example of a senior engineer letting an “agentic loop rip” on a bug, with AI-generated changes that would have badly degraded the product if merged. - The piece frames Zig’s departure as part protest, part signal: a respected project is willing to absorb migration costs to seek a more transparent and reliable platform. ## 📚 References - LeadDev: “Why Zig is moving on from GitHub” (article you’re reading). - Andrew Kelly’s blog post announcing Zig’s move from GitHub to Codeberg (primary source for his quotes and technical complaints). - Codeberg (Git hosting alternative used by Zig). - GitHub Actions official docs: conceptual background on workflows and runners. - Stack Overflow Developer Survey 2025: ranking showing Zig’s popularity. - Writings/interviews by Jeremy Howard on AI and software craftsmanship. ## 🗣️ Paraphrase - Paragraph A paraphrase. - Zig’s leader, Andrew Kelly, is removing Zig from GitHub, arguing that GitHub Actions is buggy and neglected and that GitHub’s AI-driven direction has undermined the platform’s engineering quality. - Paragraph B paraphrase. - Industry voices quoted agree that misused AI can flood projects with low-quality code and worsen technical debt, but some argue that switching platforms alone won’t fix these systemic problems. ## 📰 Newsletter A major systems-language community just sent a clear message about AI-heavy dev tooling. In “Why Zig is moving on from GitHub,” Zig’s lead calls out unreliable automation and an AI-first roadmap that sidelines craftsmanship and maintenance. For WordPress teams experimenting with AI-assisted workflows, this is a reminder: prioritize reliability, review loops, and long-term maintainability over novelty. Use AI to support good engineering practice, not replace it. ## ✅ Action Items #### DevRel - Clarify your platform’s stance on AI-assisted workflows vs. quality and reliability; prepare a concise explainer and demo. - Run office hours or workshops on “safe AI in CI/CD,” emphasizing review processes over blind automation. - Improve examples and templates for CI pipelines that include guardrails around AI-generated changes. - Publish content (talks, posts) comparing human-reviewed vs. fully automated AI change flows, with metrics on quality and incident rates. - Survey community maintainers on AI-generated PR pain points and channel feedback into roadmap items. #### OSPO - Update open-source contribution policies to address AI-generated code submissions, review expectations, and provenance. - Integrate license- and policy-aware scanning that flags AI-suspect contributions for extra review. - Define a security intake path for AI-caused regressions, including rollback and communication playbooks. - Maintain an inventory of critical automation (e.g., CI jobs, bots, AI agents) with owners and SLOs. - Budget and advocate for upstream funding to platforms and tools that prioritize reliability and transparency over lock-in. #### Community - Host maintainer roundtables on managing AI-generated contributions and setting contributor expectations. - Create contributor guides that explain when and how AI tools are acceptable, including examples of good and bad AI PRs. - For sponsors, clarify how funds support sustainable maintenance rather than chasing unstable automation trends. - Coordinate with adjacent projects on shared guidelines for AI use in contributions and code review. #### WordPress - Core: evaluate where automation helps vs. harms; keep reliability of test/build infra ahead of new AI features. - Core Performance: monitor AI-generated per - Summary: GitHub has become “completely neglected”, according to a scathing review of the platform from the project leader behind Zig. - URL: https://leaddev.com/ai/why-zig-is-moving-on-from-github [](https://leaddev.com/ai/why-zig-is-moving-on-from-github)[Article Hero – Technical direction](https://leaddev.com/ai/why-zig-is-moving-on-from-github) You have **1** article left to read this month before you need to [register](https://leaddev.com/register) a free LeadDev.com account. *GitHub has become “completely neglected”, according to a scathing review of the platform from the project leader behind Zig.* [Zig is one of the most admired programming languages](https://leaddev.com/career-development/why-zig-one-hottest-programming-languages-learn), according to [the 2025 Stack Overflow developer survey](https://survey.stackoverflow.co/2025/technology). But the man overseeing the project has chosen to pull it from the popular GitHub code repository – due to the platform leaving one of its automated AI code updating tools “completely neglected”. The project leader behind Zig, Andrew Kelly, did not immediately respond to an interview request. However, [in a blog post](https://ziglang.org/news/migrating-from-github-to-codeberg) explaining the decision, he detailed his opposition to the direction of travel GitHub was taking following its acquisition by Microsoft seven years ago. “The clock started ticking [post-acquisition],” he wrote. “’Please just give me five years before everything goes to shit,’ I thought to myself.” Kelly cited technical issues with GitHub Actions, the platform’s workflow automation system, which lets developers run scripted tasks such as building, testing, and deploying their code in response to events in a repository. “Actions has [inexcusable bugs](https://github.com/actions/runner/issues/3792#issuecomment-3182746514) while being [completely neglected](https://github.com/actions/runner/issues/385),” Kelly wrote. “After the [CEO of GitHub said to ‘embrace AI or get out’](https://www.businessinsider.com/github-ceo-developers-embrace-ai-or-get-out-2025-8), it seems the lackeys at Microsoft took the hint, because GitHub Actions started ‘vibe-scheduling’; choosing jobs to run seemingly at random,” he explained in his blog post. He’s not alone in his concerns. “If AI is deployed simply to increase the speed of which code is created without solving the quality and maintenance problems, then it’s a recipe for accelerating developer [burnout](https://leaddev.com/culture/looking-burnout) and [technical debt](https://leaddev.com/technical-direction/how-ai-generated-code-accelerates-technical-debt),” says Tom Finch, engineering leader at Chainguard. But what’s different is that Kelly chose to do something about it. “It’s abundantly clear that the engineering excellence that created GitHub’s success is no longer driving it,” Kelly wrote. “Priorities and the engineering culture have rotted, leaving users inflicted with some kind of bloated, buggy [JavaScript framework](https://leaddev.com/technical-direction/who-holds-edge-javascript-framework-wars) in the name of progress.” The move away from GitHub has garnered attention in the dev community, in part because of Zig’s (and Kelly’s) place within it. It’s also a key moment in a broader, ongoing debate about the [merits of AI within the job.](https://leaddev.com/technical-direction/trust-in-ai-coding-tools-is-plummeting) “Andrew raises many valid points,” says Guillaume Moigneu, Field CTO at cloud application platform Upsun. “Open-source contributors now face an influx of low-quality, AI-generated merge requests,” he explains. But Moigneu isn’t certain leaving GitHub is the answer. “While I fully understand the motivations of Zig’s creator to leave GitHub for a more transparent solution like Codeberg, the issues raised here need to be addressed across the industry,” he says. “A platform change won’t solve them.” Jeremy Howard, the co-founder of Answer.ai and Fast.ai, believes that AI is threatening the future of “software craftsmanship”. He says AI “encourages folks to not take the craftsmanship and the design and the architecture seriously, and instead just devolves into ‘Get my bug queue to be shallower and make the symptoms go away.’” Hey, you’d be great on the LDX3 stage But relying on agentic AI like Actions to do so can be harmful, particularly given the likelihood of errors in AI-created code. “I’ve seen a senior engineer [when] a bug gets reported and it’s like, ‘Let the agentic loop rip’, and it’s completely wrong,” says Howard. “If it had been merged, it would have made the product way worse.”, Why Zig Is Moving on From GitHub, Chris Stokel-Walker, 01kbzj2tykvxad86pek8en6xdh.