Let the tool enumerate its own refs #94
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-agent-aeb2c1c864fe8890a"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
git for-each-ref 'refs/collab/*'prints nothing and exits 0 — its globs do not cross/, while git2'sreferences_glob(which git-collab uses internally, and which the revision-ref design depends on) does. The wrong guess is silent.Adds
git-collab refs: every ref underrefs/collab/, classified — issue, patch events, patch revision, and the two superseded shapes (bare<id>, numberedr/<n>) — with a summary line answering 'does this repo hold a legacy layout?' and--jsoncarrying full ids, full OIDs, andlegacy/totalcounts.It is the one command excluded from the layout migration
runperforms on entry to every other one: a command that migrates before it looks answers its own question, always with 'none'. Tested over a repo holding both layouts at once, and asserted to leave the ref store byte-identical.git-collab-server refsis the roster-scale version for the audit blockinge5096ffc: per-repository counts, legacy refs named in full under--json, no lock or writability probe, and a non-zero exit if any repository could not be read.README's Storage section now documents which for-each-ref patterns work (
refs/collabwith no glob, orrefs/collab/**).TDD: tests/refs_test.rs written first, watched fail on 'unrecognized subcommand', then implemented. Full suite 1304 passed / 0 failed,
cargo clippy --all-targetssilent, tui_review_test run 5x with no variance (14 passed, 2.84s each).Migrated from git-collab patche
e55d15a264c00d613c740b41f8878d7b88300977.Original author: a73x dev@a73x.sh.
Fixes #89
Revision 1:
9a13fc36a85adc6fc8bf9fcd05de2f842ca6e0cf; base7a13f30a42c2d394b7a9f033b035a66e85842574