Create the workflow file
.github/workflows/unch-index.yml.To scaffold into another repository:Push and verify
Push the commit and confirm that the workflow succeeds in the repository Actions tab.
Workflow inputs
The generated workflow supports manualworkflow_dispatch inputs:
force_rebuildskip_remote_restoreskip_publish
- Repository URL bind
- Workflow URL bind
Bootstrap flows
If you want to continue gracefully when no remote artifact exists yet:--allow-missing, a missing or incompatible remote index prints a notice and exits cleanly instead of failing the flow.
Schema upgrades
When a release changes indexing or storage compatibility:- rerun the repository’s
unch-index.ymlworkflow - let CI republish a compatible
index.db,manifest.json, andfilehashes.db - run
unch remote syncor just search again locally
What does the workflow publish?
What does the workflow publish?
The generated workflow publishes
index.db, manifest.json, and filehashes.db.That gives later restores both the active index and the warm file-hash cache.What if no remote artifact exists yet?
What if no remote artifact exists yet?
Use
unch remote sync --allow-missing during bootstrap or first-run CI flows.That way a missing artifact does not fail the entire flow before the first publish exists.What should I rerun after an incompatible release?
What should I rerun after an incompatible release?
Rerun
.github/workflows/unch-index.yml so the repository republishes state compatible with the upgraded binary.