Qiniu repository migration

Code, new issues, and releases are maintained in qiniu/xhub. The initial import preserves all reachable commits and the main and dev branches from the former repository, based on main commit cc7912c8927b378e25fa7ea5e3fcd7976326218f. There were no tags or releases at migration time.

Issue mapping

The manual import preserves issue bodies, checklists, historical comments, and open/closed states. Objects are created by the migration account; attribution, original timestamps, and comment links are included in the imported text. Historical pull requests, reviews, and Actions runs remain in the former repository; their Git commits are preserved.

Publishing and server deployment

• Actions workflows are included in the code import. Image names derive from the repository: ghcr.io/qiniu/xhub-gateway and ghcr.io/qiniu/xhub-console. Publishing requires unit, backend regression, and browser E2E verification first.
• Pages uses GitHub Actions. The expected site is https://qiniu.github.io/xhub/; check the new repository's deployment results for actual availability.
• Example configuration and deployment scripts are tracked. Production configuration, supplier credentials, PostgreSQL, Redis, and user accounts remain on the server and are preserved in place, with private server-side backups. Runtime reports and test credentials are excluded from Git.
• The existing Go module identity github.com/sunqirui1987/xhub and internal imports remain compatible. This does not prevent builds or releases from the new repository. A public module rename should be assessed separately for downstream consumers.

Developer remotes

Keep the former remote as legacy if needed and point the primary remote to the new repository:

git remote set-url origin git@github.com:qiniu/xhub.git
git fetch origin

Check uncommitted changes first. Server updates pin verified image digests rather than following mutable main tags.