huggingface-git-xet-dataset-publisher

Manages Hugging Face dataset Git repositories with Xet tracking, snapshot pushes, and binary rejection recovery.

2|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/zero-yx/static_flow --skill huggingface-git-xet-dataset-publisher-zero-yx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: huggingface-git-xet-dataset-publisher
Source: https://github.com/zero-yx/static_flow/tree/main/skills/huggingface-git-xet-dataset-publisher
Command: npx skills add https://github.com/zero-yx/static_flow --skill huggingface-git-xet-dataset-publisher-zero-yx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing large binary dataset artifacts (such as LanceDB snapshots) to Hugging Face Git repositories often fails with binary rejection errors, inconsistent tracking rules, and diverged branches. This Skill provides a complete operational playbook for setting up Git Xet tracking, committing safe snapshots, and recovering from failed pushes. ## Core Features & Use Cases - Repository Setup & Bootstrap: Initialize or bind a local data folder to a Hugging Face dataset remote, whether the remote already has history or is empty, and configure Git Xet tracking for binary extensions like .lance, .txn, .manifest, and .idx. - Daily Snapshot Workflow: Commit and push dataset updates safely with preflight checks for branch divergence, remote state, and tracking rules. - Binary Rejection Recovery: Diagnose and fix pre-receive hook rejections caused by untracked binary files, including branch surgery and clean-branch publication strategies. - Use Case: You maintain a LanceDB database synced to a Hugging Face dataset repo. A push fails with "Your push was rejected because it contains binary files" for .idx files. Use this Skill to add the missing Xet track rule, realign local main to the remote tip, re-commit, and push successfully. ## Quick Start Set up my local LanceDB data folder as a Hugging Face dataset Git repository with Xet tracking and push the initial snapshot to the remote.

Frequently Asked Questions about huggingface-git-xet-dataset-publisher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I push large binary dataset files to Hugging Face?▼

Use Git Xet tracking for binary extensions before committing. Run git xet install, then git xet track for each binary pattern such as *.lance, *.txn, *.manifest, and *.idx, then stage, commit, and push to the dataset remote.

How to fix Hugging Face push rejected because it contains binary files?▼

Check the offending file with git check-attr filter to see if it is tracked. If it shows filter: unspecified, add a track rule with git xet track for that extension, then realign local main to origin/main, re-commit, and push again.

How do I turn an existing non-Git data folder into a Hugging Face dataset repo?▼

Run git init in the folder, add the Hugging Face SSH remote, and fetch origin main. If the remote has history, check out main from origin/main; if empty, initialize with git init -b main, then enable Xet tracking and push.

Does Git Xet use the same .gitattributes filter as Git LFS?▼

Yes. On Hugging Face, Git Xet tracking writes filter=lfs rules into .gitattributes, which is the expected configuration. Files tracked this way appear as LFS pointers and can be verified with git lfs ls-files.

When should I pause writers before committing a LanceDB snapshot?▼

Pause writers whenever the source data is actively being written, such as a live LanceDB instance. Committing during active writes can produce inconsistent snapshots, so stop writers before staging and pushing the snapshot.