GitHubVFS exposes a single repository at a ref as a read-only
filesystem. Reads stream blobs through GitHub’s
REST API; it does not imitate another CLI.
Setup steps for the personal access token live at GitHub Credentials.
Node
create fetches the repo’s git tree before it
builds the VFS, so it has to be awaited. Python deliberately differs
here: GitHubVFS(...) is an ordinary call that contacts nothing, and
hydrates the tree on first read, which is what lets its build_vfs
stay synchronous.
Browser
Config
Listings under fresh
Under read: fresh, a cached listing is checked against the head commit
the ref resolves to: one small check per command (a shallow
git/trees/{ref}), after which every cached listing of the mount at that
commit is served. A mount whose ref is a full 40- or 64-hex commit sha
serves its cached listings with no request: github.com refuses a branch or
tag named with 40 or 64 hex characters, so such a ref always names a commit
(a GitHub Enterprise host is assumed to do the same). A repository whose recursive
tree comes back truncated stores no version, so each folder is re-listed
once per command. See
listings under fresh.
Mount mode
read. Writes are not yet exposed.
For the mounted layout (refs, paths, blob caching) see the Python GitHub docs.