Use Xet Storage#

Use Xet through MEGA's ordinary repository tools. For most workflows, select a repository, keep the source tree stable while it transfers, and use a commit or tag when the release is ready.

Install Git-Xet#

Install MEGA's Git-Xet build from the stable installer endpoint:

1curl -sSfL https://mega.tensorplay.cn/git-xet/install.sh | sh2git xet --version

The installer registers xet for uploads and xet-download for downloads. Both operations transfer large-file bytes directly between Git-Xet and the Xet CAS returned by MEGA; the Hub and Git Gateway only negotiate scoped actions and tokens. Older Git-Xet clients remain compatible and use the signed basic download path when they do not advertise xet-download.

Upload a large release tree#

Use the resumable uploader for large directories:

mega upload-large-folder OWNER/REPOSITORY ./release --revision main

Run the command again with the same source and destination after an interruption. Do not start several uploads into the same destination at once. Once the release is verified, add an explicit tag for consumers.

Download a release#

Download a complete revision with an explicit tag or commit:

mega snapshot OWNER/REPOSITORY --revision v1.0 --local-dir ./release

Keep the manifest, configuration, and artifact files together. For selected files or small changes, use the repository commands in Hub Repositories.

Work with Git#

Standard Git repository workflows continue to work for MEGA repositories:

1git clone https://git.tensorplay.cn/OWNER/REPOSITORY.git2cd REPOSITORY3git add .4git commit -m "Publish release"5git push origin main

Use Git LFS Compatibility when an existing project or automation already relies on Git LFS tooling.

Choose the right storage target#

Use a repository for release assets that need history and review. Use a Storage Bucket for mutable job output, checkpoints, or files synchronized in place.