FreeBSD ports freeze: Copilot binary commit broke GitHub mirror

Key Takeaways

• A developer accidentally committed the Copilot CLI binary to FreeBSD's ports repository, triggering a two-day freeze
• The 100MB+ file broke GitHub's automated mirroring due to hard file size limits
• The incident highlights ongoing usability challenges with Git that drive interest in alternatives like Game of Trees

FreeBSD froze its ports repository for two days this week after a developer accidentally committed an entire Microsoft Copilot binary to the tree. The 100MB+ file exceeded GitHub's hard size limit, severing the automatic mirror sync and forcing maintainers to clean up the repository history.

The freeze announcement went out on July 21 and remained in effect through July 22. A message on the freebsd-announce mailing list explained the situation with characteristic understatement: "The commit in question severed our ports tree mirroring to github.com due to their filesize hard limit of 100MB, and introduced a blob of questionable licensing into the repository history."

What exactly went wrong?

FreeBSD's ports collection is a package management system that lets users compile and install third-party software. The tree gets mirrored automatically to GitHub for broader accessibility. GitHub enforces a strict 100MB file size limit on all repositories. When the Copilot binary exceeded that threshold, the mirroring pipeline broke.

There's an existing FreeBSD port for Copilot, but FreeBSD terminology creates some confusion here. The "port" is a package that runs the Linux binary inside FreeBSD's Linux emulation layer, called the Linuxulator. It's not a native FreeBSD build. The package isn't supposed to include the actual Copilot CLI binary, partly because that binary carries its own custom license. FreeBSD's Kyle Evans referenced this as "questionable licensing" in the announcement.

Why does this keep happening with Git?

The incident is less about one developer's mistake and more about Git's persistent usability problems. Git has become the de facto version control system for open source, but its complexity trips up even experienced contributors. The tool isn't an acronym. It's British slang for an annoying person. The name fits the experience many developers report.

The XKCD comic about Git captures the reality: most developers memorize a handful of commands and pray nothing breaks. When something does break, they delete the repo and clone fresh. This isn't a joke workflow. It's how people actually cope.

Git alternatives gaining traction

Multiple teams are building Git-compatible alternatives that prioritize usability. The day before FreeBSD's mishap, Game of Trees released version 0.127. Developed by OpenBSD contributors since 2019, Got (as it's called) explicitly positions itself against Git's philosophy.

Git's homepage says it handles "everything from small to very large projects with speed and efficiency." Got's homepage counters with: "a version control system which prioritizes ease of use and simplicity over flexibility." The FAQ is even blunter. Under a section anchored "pointless," it asks: "What's the point of all this? Why not just use Git?" The answer: "If you are wondering why Got even exists, you can just ignore it."

Gitless describes itself as "a simple version control system built on top of Git" but development stalled in 2019. Jujutsu, often called Jj, remains actively developed but assumes familiarity with Git concepts. For newcomers, Remo Senekowitsch's guide "Jujutsu for Everyone" provides a gentler onramp.

The licensing wrinkle matters for enterprises

Beyond the technical breakage, the "questionable licensing" flag carries weight for IT leaders. The Copilot CLI binary ships under Microsoft's custom license, not an OSI-approved open source license. Accidentally embedding proprietary binaries into open source repositories creates compliance headaches. License scanners would flag this. Auditors would ask questions.

FreeBSD's ports system is designed to avoid exactly this situation. The port definition tells FreeBSD where to fetch the binary and how to run it. The binary itself lives on Microsoft's servers. Committing the actual binary broke that separation.

How did FreeBSD fix it?

Cleaning a large binary from Git history requires rewriting commits. Tools like BFG Repo-Cleaner or git filter-branch can purge files, but the process forces all downstream mirrors and clones to resync. The freeze gave maintainers time to scrub the binary, verify the history, and let mirrors catch up.

For most organizations, a two-day freeze would be disruptive but manageable. For FreeBSD's ports tree, which developers worldwide depend on for package builds, it meant pausing contributions until the repository stabilized.

Frequently Asked Questions

What caused the FreeBSD ports repository freeze?

A developer accidentally committed a Microsoft Copilot binary that exceeded GitHub's 100MB file size limit, breaking the automated mirror sync and introducing licensing concerns.

What is GitHub's file size limit?

GitHub blocks files larger than 100MB from being pushed to repositories, enforcing this as a hard limit.

What is Game of Trees (Got)?

Got is a Git-compatible version control system developed by OpenBSD contributors that prioritizes simplicity over Git's flexibility. Version 0.127 released in July 2026.

How do you remove large files from Git history?

Tools like BFG Repo-Cleaner or git filter-branch can purge large files, but the process rewrites commit history and requires all clones and mirrors to resync.

Why can't Copilot be included directly in FreeBSD ports?

The Copilot CLI binary uses Microsoft's custom license, not an OSI-approved open source license. FreeBSD ports reference external binaries rather than embedding proprietary code.

Source: www.theregister.com