The artifact hash prefix 0c0a0 is ambiguous and might mean any of the following:
0c0a02a14422027ca1388e7e432b3df381618d9668a3d051f25572f425c4fcc7 -
0c0a061f4d74d443fbc36787ed0e94c156985596b4bb2ffd1d846e53954ab043 -
- File
cmd/quarry/registrar.go
— part of check-in
[a8d2831bf4]
at
2026-08-18 11:42:29
on branch trunk
— repo.delete: destroy a repository, with two brakes
Removing a repository's disk space meant going to the shell and doing it without quarry knowing, which is worse than quarry doing it. Deletion now purges the store, the derived index, and every forge row keyed to the repository — grants, sync users, mirror, webhooks, CI records — in one transaction, so a new repository of the same name cannot inherit somebody's credentials.
Two brakes. confirm must equal the name: a yes/no prompt is answered reflexively, typing the name requires having read which repository is about to go. And the store is removed ONLY when it lives under this node's repositories root — quarry serves stores it did not create, and this forge runs on a corpus of exactly those, so deleting one named by --repo would destroy a checkout somebody else manages. Verified: the attempt on pikchr refuses and says to unregister instead. (user: dmestas, size: 19605) [annotate] [blame] [check-ins using]
- File
cmd/quarry/registrar.go
— part of check-in
[a8d2831bf4]
at
2026-08-18 11:42:29
on branch trunk
— repo.delete: destroy a repository, with two brakes