Yeelight China Mirror Sync

简体中文

Official GitHub Actions automation for mirroring every public repository in the Yeelight organization to:

• Gitee, the recommended mainland China mirror
• GitCode, an additional mainland China mirror
• GitLab.com, a global fallback mirror

GitHub remains the canonical source for development, issues, pull requests and releases. Target repositories are read-only distribution mirrors.

What Is Mirrored

• All current and future public repositories discovered through the GitHub API, including archived repositories and forks
• refs/heads/*, refs/tags/* and refs/notes/*, protected by per-ref leases
• Portable repository metadata and Wiki Git when supported
• All release metadata; latest stable assets at initial adoption and every new release asset after the configured cutover date

Objects without portable identity or semantics, including issues, pull requests, stars, Actions, packages and secrets, are explicitly not copied.

Gitee currently limits each Release to 20 attachments. The synchronizer keeps a deterministic installable subset and reports omitted files as unsupported. Gitee's scanner also rejects the official yeelight-home-windows-arm64.zip; that verified asset remains available from GitHub, GitCode, and GitLab.com.

Safety Model

GitHub is authoritative: target-side drift is detected and force-converged with an observed-value lease, including deletion of target-only mirrored refs and Release objects. A concurrent write still fails the lease and is retried on the next run. Credentials are read from GitHub Actions Secrets or a local credential provider and never embedded in Git URLs, state, reports or repository configuration. See Architecture, Operations and Security.

Local Verification

npm test
node src/cli.mjs plan --platform all --repository all

sync performs remote writes and requires the platform Token and username environment variables documented in Operations.

License

Apache License 2.0.