npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/bin/ngit/sub_commands/sync.rs, branch v2.2.3

fix: skip ^{} peeled-tag refs in sync to prevent invalid refspec crash

2026-02-27T17:19:20+00:00

Regression introduced in 28ad5440: ngit sync crashed with 'invalid refspec refs/remotes/origin/v1.4.4^{}:refs/tags/v1.4.4^{}' on repos with annotated tags. Fixed by guarding all three iteration sites in sync.rs and identify_remote_sync_issues in list.rs; also corrected the always-false logic bug in invalid_nostr_state_ref.

feat: ngit sync --force republishes state event even with no ref changes

2026-02-27T15:53:11+00:00

allows users to repair repos whose state event is missing ^{} peeled refs for annotated tags (or any other corruption) without needing to push a new ref. the new event is signed with a fresh timestamp and broadcast to all repo relays and the user's write relays.

feat: publish state event to stale grasp relays before sync push

2026-02-26T15:26:18+00:00

FetchReport now captures the full state event seen on each relay during the nostr fetch (state_per_relay: HashMap>). ngit sync uses this to identify grasp server relays with a missing or outdated state event and publishes the current state event to them before attempting git pushes, preventing rejections. An existing login is loaded silently (no prompt, no profile fetch) to provide a signer for NIP-42 auth if requested.

fix: correct refspec source in ngit sync to strip refs/heads/ prefix

2026-02-26T15:26:15+00:00

When syncing, the nostr state stores refs with full names like refs/heads/master and refs/tags/v1.0.0. Git tracking refs strip the refs/heads/ prefix, so the tracking ref lives at refs/remotes/origin/master not refs/remotes/origin/refs/heads/master. The sync code was interpolating the full nostr_ref_name into the source side of the refspec, producing the invalid double-prefixed path. Strip refs/heads/ or refs/tags/ before constructing the tracking ref segment, consistent with how git_remote_nostr/push.rs already handles this.

feat: forward unrecognised push options to git servers

2026-02-26T15:26:14+00:00

Any -o option passed to `git push` that is not handled by ngit (title, description) is forwarded verbatim to the git server via git2::PushOptions::remote_push_options. This allows options such as `-o secret-scanning.skip` to pass through transparently. `ngit send` gains a matching -o / --push-option flag for the same purpose.

feat(list): make list async and include sync report inline

2025-11-13T22:08:56+00:00

copy relay fetching approach to async and reporting

refactor: simplify get_short_git_server_name

2025-11-13T14:55:50+00:00

so it doesnt use the git_repo

fix: cli output line deletion during fetch

2025-11-13T14:40:09+00:00

also reduce the clutter in the cli output for grasp servers.

fix: grasp server detection

2025-10-20T13:36:24+00:00

to ensure we dont try and fallback to ssh

fix(sync): dont fetch tags available locally

2025-09-12T08:01:01+00:00

as it was only checking if tip is a commit thats present but a tip could be an annotated tag