xet-core

mirror of https://github.com/huggingface/xet-core.git synced 2026-06-04 13:30:29 +08:00

Files

Adrien 0fb930c8d0 feat: expose skip_sha256 parameter in Python upload API (#705 )

## Summary

Add `skip_sha256` and `sha256s` parameters to `upload_bytes()` Python
binding for per-file SHA-256 policies:
- `skip_sha256: bool = False` - Skip SHA-256 computation entirely (sets
`Sha256Policy::Skip`)
- `sha256s: Optional[List[str]] = None` - Provide pre-computed SHA-256
hashes (companion to existing parameter on `upload_files()`)
- These parameters are mutually exclusive

## Changes

**Python binding changes:**
- Add `skip_sha256` + `sha256s` params to `upload_bytes()` /
`upload_files()`
- All policy conversion happens at Python boundary

**Internal refactoring:**
- Add `Clone`/`Copy` derives + `from_skip()`/`from_hex()` helpers to
`Sha256Policy`
- Update `upload_bytes_async`, `upload_async`, `clean_file` to use
`Vec<Sha256Policy>`
- Update all internal callers across `git_xet`, `xet_pkg`, migration
tool, tests

## Motivation

`huggingface_hub` already knows whether SHA-256 is required. This change
enables skipping expensive computation when unnecessary, or passing
pre-computed hashes for bulk operations.

Companion to #678.

---------

Co-authored-by: Wauplin <lucainp@gmail.com>

2026-03-12 18:17:12 +01:00

src

feat: expose skip_sha256 parameter in Python upload API (#705 )

2026-03-12 18:17:12 +01:00

tests

Integration test for ssh access on Windows (#566 )

2025-11-20 03:22:19 -08:00

windows_installer

Upgrade git-xet to 0.2.1 (#653 )

2026-02-12 15:45:34 -08:00

Cargo.toml

Code reorganization towards release of xet cargo package (#693 )

2026-03-11 12:02:38 -07:00

entitlements.xml

Build and release git-xet (#499 )

2025-09-22 15:44:02 -07:00

install.sh

Update git-xet install URls (#655 )

2026-02-12 16:40:40 -08:00

README.md

Update git-xet install instructions (#583 )

2025-12-02 16:04:20 -08:00

README.md

Git-Xet is a Git LFS custom transfer agent that implements upload and download of files using the Xet protocol. Install git-xet, follow your regular workflow to git lfs track ... & git add ... & git commit ... & git push, and your files are uploaded to Hugging Face repos using the Xet protocol. Enjoy the dedupe!

Installation

Prerequisite

Make sure you have git and git-lfs installed and configured correctly.

macOS or Linux (amd64 or aarch64)

To install using Homebrew:

brew install git-xet
git xet install

Or, using an installation script, run the following in your terminal (requires curl and unzip):

curl --proto '=https' --tlsv1.2 -sSf https://raw.githubusercontent.com/huggingface/xet-core/refs/heads/main/git_xet/install.sh | sh

To verify the installation, run:

git xet --version

Windows (amd64)

Using winget:

winget install git-xet

Using an installer:

Download git-xet-windows-installer-x86_64.zip (available here) and unzip.
Run the msi installer file and follow the prompts.

Manual installation:

Download git-xet-windows-x86_64.zip (available here) and unzip.
Place the extracted git-xet.exe under a PATH directory.
Run git-xet install in a terminal.

To verify the installation, run:

git xet --version

Uninstall

macOS or Linux

Using Homebrew:

git xet uninstall
brew uninstall git-xet

If you used the installation script (for MacOS or Linux), run the following in your terminal:

git xet uninstall
sudo rm $(which git-xet)

Windows

If you used winget:

winget uninstall git-xet

If you used the installer:

Navigate to Settings -> Apps -> Installed apps
Find "Git-Xet".
Select the "Uninstall" option available in the context menu.

If you manually installed:

Run git xet uninstall in a terminal.
Delete the git-xet.exe file from the location where it was originally placed.

How It Works

Git-Xet works by registering itself as a custom transfer agent to Git LFS by name "xet". On git push, git fetch or git pull, git-lfs negotiates with the remote server to determine the transfer agent to use. During this process, git-lfs sends to the server all locally registered agent names in the Batch API request, and the server replies with exactly one agent name in the response. Should "xet" be picked, git-lfs delegates the uploading or downloading operation to git-xet through a sequential protocol.

For more details, see the Git LFS Batch API and Custom Transfer Agent documentation.