Fix #301: per-entry last-commit dates #308
No reviewers
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub!308
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/issue-301"
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?
Fixes #301 — the Code tab stamped the repo HEAD date on every tree row. TreeEntry gains
commit_sha+commit_time(omitempty, additive JSON), computed by ONE batchedgit logwalk per listing (first-parent, --no-renames, -z, --max-count=server.max_tree_log, default 200); submodules and capped entries stay dateless with a neutral em-dash fallback. Tree.jsx drops the HEAD-stamp proxy (extra commits?n=1 fetch gone — zero extra round trips). Payload stays sha-pure (ETag/SWR unchanged), zero store round trips added, fail-open on walk errors. Tests: table-driven assignment (newest-wins, subdir prefix, cap, submodules, malformed, 1-char paths) + real-git integration + setup round-trip + bound validation; api/config -race green, e2e green, node suite green (8 env-only marked-package failures pass with node_modules present), vite build green. Docs: 07_api §9.4 + Decisions, 04_git argv registry, 11_config_cli key row, 12_web_ui entry. Browser proof open (shared-daemon loopback guard).