A branch that cannot be backed up

The nightly snapshot bundles every repository (src/snapshot/bundle.ts). A branch whose history is not all there (a commit, tree or blob it reaches is missing) cannot go in a bundle. The snapshot keeps the rest of the repository and names that branch. The forge's admin then sees one card for each such repository, on the vitals and the home:

1 branch of owner/name cannot be backed up: their commits are missing (name).

The rest of the repository is in the snapshot. Re-push each from a clone that

still has its commits, or delete it on the branches page; the repository's

owner or a writer can.

To clear it: open the card. It links to the repository's Branches page, /owner/name/branches, and each branch it names links to its own row there (#branch-<name>). The owner or a writer presses Delete on that row. Pushing the branch again from a clone that has every object also works. A site admin writes every repository, so the admin who reads the card can press it too. The card goes away when the next snapshot lands without the branch.

never runs gc, so its tip commit stays in the object store, where someone on the box can read it with git cat-file -p <oid>.

fork borrows, and a missing object makes that repack fail.

fails on the server with bad tree object <oid> (or a missing commit or blob). Fetching the refs in halves finds the one that fails.

The first case was mason/forge on 2026-11-14 (#12581). The branch was mason/7731-palette-entries-can-live-beside-their-sc, tip 443cf57e. Its tree 6d6a9f68 was missing. Its run had ended with nothing to merge, so deleting it lost no work.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs