Repository navigation
README: give every feature an honest status marker - #74
Merged
Merged
Conversation
Core Operations carried ✅/🧭 markers while Advanced Operations were listed flat with no status at all, and a duplicated block under "Administrative" marked most of those same advanced features 🧭 — understating them, since submodules, sparse checkout, rerere, repack, object replacement, bisect, blame, stash, grep and the rest all ship as callable functions in sql/pgit-*.sql. The section also listed the same features twice and had two "Administrative" headings. Rewrite the whole Features section as one marked list, with the function names spelled out the way Core Operations already did. Two markers were not enough. Several features are exported and callable but have a placeholder at their centre, and calling those ✅ would oversell them exactly as badly as calling them 🧭 undersells the rest, so add⚠️ with a note naming the missing part: - create_archive concatenates blob contents behind placeholder tar/zip headers, so the output is not a valid archive; - verify_commit / verify_tag check trust levels but do no cryptographic verification — any stored signature is reported valid; - start_instaweb records config and returns a URL without starting a server; - merge_branches raises on divergent history (fast-forward only); - push resolves the ref and raises a notice without transferring anything. The last two are in Core Operations, which previously listed them under an "(Implemented)" heading with no qualification. Also add features that shipped but were never documented (bundles, merge_trees, commit notes, the cat_file/hash_object/ls_tree/rev_list plumbing set, which the old text listed as planned), and mark reflog and fsck 🧭 since nothing in sql/ implements them. Every function name in the new list was checked against sql/pg_git--0.4.0.sql. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017nq3xZcPqSTKtskyP2DzkK
seanwevans
deleted the
claude/pg-git-upgrade-deps-rk0oxk-readme-status
branch
September 3, 2026 23:03
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The problem
Core Operations carried ✅/🧭 markers while Advanced Operations were listed flat with no status at all.
Investigating to add the markers turned up more than asymmetry:
sql/pgit-*.sql.### Administrativeheadings.merge_trees, commit notes), and the plumbing setcat_file/hash_object/ls_tree/rev_listwas listed as planned when all four are shipped.The fix
One marked list, with function names spelled out the way Core Operations already did.
Two markers were not enough. Several features are exported and callable but have a placeholder at their centre, and calling those ✅ would oversell them exactly as badly as 🧭 undersells the rest. So there is now a⚠️ tier, with a note naming the missing part:
create_archivetar/unzipverify_commit/verify_tagstart_instawebmerge_branchesOnly fast-forward merges are currently supportedon divergent historypushThe last two are in Core Operations, which previously listed them under an "(Implemented)" heading with no qualification.
Reflog and fsck are marked 🧭 — nothing in
sql/implements them.Verification
Every function name in the new list was checked to exist in⚠️ notes are each traceable to a specific placeholder in the source (
sql/pg_git--0.4.0.sql; the-- In a real implementation, this would...,-- For now, we'll assume any stored signature is valid,-- tar file header (simplified)).Docs only — no code changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_017nq3xZcPqSTKtskyP2DzkK
Generated by Claude Code