npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/lib/git, branch v2.4.3

fix: percent-encode identifier in nostr:// URLs and GRASP HTTP paths

2026-04-10T16:30:02+00:00

Repository identifiers can contain any characters per NIP-01 d-tag rules. Encode them in nostr:// clone URLs (display and parse) and in GRASP //.git paths, aligning with NIP-34 and GRASP-01.

feat: git worktree support

2026-03-30T16:29:23+00:00

Git worktrees don't have a .git directory with a parent, so we need to look for the git dir via git2's Repository::discover() and then look for the cache database there. This allows the client to work correctly when run from a worktree, and also allows the cache database to be shared between the main repo and its worktrees (since they share the same git dir and thus the same cache path).

fix(patch): accept reconstructed OID when commit id mismatch occurs

2026-03-30T16:29:22+00:00

When applying a patch, if the reconstructed commit OID doesn't match the tagged commit id (after the existing amend attempt), accept the reconstructed OID rather than erroring. The diff is applied correctly regardless of the mismatch; apply_patch_chain already threads the actual OID forward via next_parent_override so the chain remains consistent. Mismatches can occur for several reasons: GPG-signed commits where libgit2's commit_create_buffer produces subtly different bytes than the original git commit, patches produced with non-standard tooling, or edge cases like the diff.noprefix issue fixed in 7a36aed.

fix(patch): don't error on commit id mismatch for pgp-signed commits

2026-03-30T16:29:20+00:00

When applying a patch with a pgp signature, commit_create_buffer + commit_signed reconstructs the signed commit object. The resulting OID matches the original only if commit_create_buffer produces the exact same bytes that git originally signed — which isn't guaranteed across different git implementations or versions. The existing amend workaround (which re-applies author/committer to recover the correct OID) is preserved for unsigned commits. For pgp-signed commits the amend still runs but the mismatch bail is skipped, since the tree, author, committer, message and signature are all correct regardless of the OID difference.

fix(patch): handle diff.noprefix and normalize non-standard diff paths

2026-03-30T16:29:19+00:00

libgit2 respects the user's `diff.noprefix` git config when generating patches via `git_email_create_from_commit`, producing diffs without the standard `a/`/`b/` path prefixes. `git2::Diff::from_buffer` always expects the standard prefix format and fails with "header filename does not contain 1 path components" when it is absent. Two fixes: - In `make_patch_from_commit`: explicitly set `old_prefix("a/")` and `new_prefix("b/")` on the diff options so ngit always generates interoperable patches regardless of the submitter's git config. - In `create_commit_from_patch`: normalize no-prefix diffs before passing to `git2::Diff::from_buffer`, as a defensive measure for patches already published by affected ngit versions or other tools. Adds unit tests for the normalization function covering: no-op on already-prefixed diffs, single and multi-file patches, new/deleted files (/dev/null preservation), and end-to-end libgit2 parse verification.

fix(whoami): detect and fall back to system git config for nostr login

2026-03-05T15:06:02+00:00

Add GitSystem to SignerInfoSource so credentials stored in the system git config (/etc/gitconfig) are included in the priority fallback chain (local > global > system) and shown as a separate level in whoami output.

fix: update hardcoded libgit2 version strings in tests to 1.9.2

2026-02-25T12:27:56+00:00

The Nix environment provides libgit2 1.9.2 via nixpkgs, which libgit2-sys picks up at build time instead of using its bundled version. This caused test assertions that hardcode the libgit2 version string (appended by libgit2 to patch output) to fail after commit 319bb7f added new Cargo dependencies, though the exact mechanism by which those dependencies triggered the switch from the bundled 1.9.1 to the system 1.9.2 remains unclear. Also bump git2 from 0.20.2 to 0.20.4 in both Cargo.toml files so the bundled libgit2-sys version (0.18.3+1.9.2) properly aligns with the 1.9.2 version in use.

fix: thread applied OID through patch chain correctly

2026-02-18T21:17:41+00:00

When applying a chain of patches without parent-commit tags, each patch's parent was resolved independently, meaning patch2 would not parent off the OID patch1 actually produced. Thread next_parent_override through the loop and guard the early-return in create_commit_from_patch so the override is always honoured.

fix: harden apply_patch_chain when optional patch tags absent

2026-02-18T21:04:59+00:00

- Replace .unwrap() calls in filter closure with pattern-let guards so a missing/invalid mbox commit id conservatively includes the patch - Use the OID returned by create_commit_from_patch as branch tip instead of the tag commit id, which may differ for GPG-signed commits - Add module-level doc comment to mbox_parser explaining design rationale and known limitations around the mbox envelope SHA1

feat: handle missing optional patch tags for pr/ flow

2026-02-18T14:48:20+00:00

- Add mbox_parser module to extract metadata from patch content - Extract author/committer from From: and Date: headers when tags missing - Extract commit message body as fallback for description tag - Implement best-guess parent commit logic using committer timestamps - Update patch_supports_commit_ids to accept mbox-parseable patches - Enable patches without optional tags to appear as pr/ branches