Oniro WG: OpenHarmony migration & GitHub mirror sync failure
Summary
The upstream OpenHarmony project has fully migrated its primary repository location from Gitee to GitCode (https://gitcode.com/openharmony). While we successfully updated most CI/mirroring workflows, a critical error is preventing the complete synchronisation of our code mirrors on GitHub.
This failure is impacting the availability of necessary code for developers and requires a decision from our side (IT team) regarding our GitHub plan.
Technical problem & impact
| Issue | Details | Consequence |
|
Mirror failure |
The repository |
Incomplete, unreliable code availability for developers using GitHub as their primary source. |
|
Root cause |
The failure is due to GitHub’s LFS limit of 2GB. The failing repository contains LFS files that exceed this cap. | We cannot maintain a true, complete mirror of the official OpenHarmony codebase under our current GitHub plan. |
|
New upstream |
OpenHarmony confirmed the full migration to GitCode on September 15, 2025. The original Gitee link now serves as a mirror. | All infrastructure decisions must prioritize GitCode as the new source of truth |
Required action & IT decision
Is it possible to resolve this blockage by determining the cost and feasibility of upgrading our current GitHub plan to support LFS files greater than 2GB? This would allow full mirroring.
Upstream source (new): https://gitcode.com/openharmony
Migration instructions (original source): https://gitcode.com/openharmony_infra/infrastructure/blob/master/zh/migrate.md