npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/src/git/subprocess.rs, branch v1.0.1Unnamed repository; edit this file 'description' to name the repository.
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/atom?h=v1.0.12026-01-12T14:05:51+00:00feat: add uploadpack.allowFilter support for GRASP-01 compliance2026-01-12T14:05:51+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-12T14:05:51+00:00urn:sha1:817ce37a5ee8d6279a44cf8cce3cc6a1e4bab576
Add mandatory uploadpack.allowFilter capability to support partial clones
and fetches as required by GRASP-01 specification. This enables efficient
git operations for bandwidth-constrained clients (e.g., browser-based git
clients like git-natural-api).
Changes:
- Add uploadpack.allowFilter=true to git subprocess configuration
- Update SmartGitServer test helper with filter support
- Add integration tests for filter capability advertisement and functionality
- Update documentation to reflect filter as required capability
Tests verify:
- Filter capability is advertised in info/refs
- Filtered clones with blob:none work correctly
- Filtered fetches with tree:0 work correctly
Add Git protocol v2 support to fix modern git client compatibility2026-01-07T21:35:56+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-07T21:35:56+00:00urn:sha1:457e296d90e2f7c2808e216f2ef0608b70f76553
Modern git clients (2.51.0+) default to protocol v2 and send the
Git-Protocol header. The server must pass this to git processes via
the GIT_PROTOCOL environment variable for proper negotiation.
Changes:
- Extract Git-Protocol header in HTTP layer (src/http/mod.rs)
- Pass git_protocol parameter through all handler functions
- Set GIT_PROTOCOL env var when spawning git subprocesses
- Update all tests to pass None for backward compatibility
This fixes hangs/timeouts when modern git clients connect to the server.
Fixes issue discovered in work/2025-01-07-pr-clone-tag-sync-investigation.md
fix cargo clippy and fmt warnings2025-12-01T15:22:38+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-01T14:31:32+00:00urn:sha1:d2ac69816567f092fe0d4661723bc43778cb481badd git http advertisment allow-reachable-sha1-in-want and allow-tip-sha1-in-want2025-11-28T03:38:21+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-28T03:38:21+00:00urn:sha1:3f74ababf338d65ac5e29e7eb5541ce416b7fe75fixed http clone2025-11-21T15:35:19+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-21T15:35:19+00:00urn:sha1:ee7e115b2d0e6a6eee42eb875199c965696017d5
but do we really nedd to create a blank commit?
I dont think ngit-relay does that.
Do we need to se the default branch or is this automatic?
add git http handling2025-11-21T13:37:57+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-21T13:37:57+00:00urn:sha1:9a8c551adfada379704d594a6ff3862f13857b8e