2fa8090568
An independent live review of the tidy found it could lose data: a merge under pack.packSizeLimit published only the first of several output packs (45 of 60 commits gone), erasing "commit-free" on-demand packs dropped trees and blobs a local branch still needed once upstream had pruned them, a process killed mid-erase left a multi-pack-index naming a deleted pack, and a classification timeout was cached as "holds commits" forever. The erase rule is now proof against local packs alone: a promisor pack goes only when every object in it is also in another promisor pack (checked by binary search over the .idx files, no git process per pack). Nothing stored locally can be lost and nothing depends on the remote still serving it, so the marker heuristics and commit classification are gone. Merges run with pack.packSizeLimit=0 and refuse anything but exactly one output; the multi-pack-index is dropped before any pack is removed, so a kill at any point leaves git reading; a lock file keeps two tidies from each erasing a pack because the other still holds its copies. .keep files written by a fetch-pack/index-pack that died (older than an hour) no longer pin their packs. git's own repack never touches .keep'd packs, and on a real dev checkout 53 of them held 4.5 GB of duplicated history downloads.
Website
This website is built using Docusaurus, a modern static website generator.
Reading the docs on GitHub? The Markdown under
docs/is authored for the rendered site at https://hermes-agent.nousresearch.com/docs/. Cross-page links are relative Markdown paths, so they follow through on GitHub's file viewer too. Every page on the site has an Edit this page link that opens the source file here.
Authoring links in docs/
- Link to another page with a relative Markdown path, anchors included:
[Profiles](../user-guide/profiles.md),[Bundles](../user-guide/features/skills.md#skill-bundles). Docusaurus turns the file path into the page route; GitHub follows the same path. Site routes (/user-guide/profiles,/docs/user-guide/profiles) only work on the rendered site — GitHub resolves them as repository paths and 404s, and the/docs/form also emits/docs/zh-Hans/docs/...404s in the zh-Hans build becausebaseUrlis already/docs/. python3 website/scripts/check_doc_links.pyfails on any route-style link in hand-authored pages (EN and the zh-Hans mirror);--fixrewrites them. It runs in theDocs Site Checksworkflow. Generated pages (user-guide/skills/{bundled,optional},reference/*skills-catalog.md) are produced byscripts/generate-skill-docs.py, which emits the same relative form.- Pin
{#anchor}on cross-linked headings so the zh-Hans mirror keeps the same id.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.