npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/src/lib/push.rs, branch v2.2.3

fix: report per-relay publish results in send_events summary

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

Change send_events() return type from Result<()> to Result> so callers can inspect which relays accepted events. Update the finish message to show "Published to X/N relays (failed: ...)" instead of the unconditional "Published ... to nostr relays".

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.

refactor: simplify get_short_git_server_name

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

so it doesnt use the git_repo

fix(pr): push use stderr rather than stdout

2025-10-28T11:00:50+00:00

so we dont return a value to the git during remote helper operations

feat!(nostr_url): replace user with ssh_key_file

2025-10-17T11:18:24+00:00

replaces the "user" in the nostr_url format with "ssh_key_file", to support the original intent, which was to allow users to specify different authentication credentials. most git servers always expect the ssh user to be 'git'. the idiumatic way of specifying logging in as a different user is to specify a different ssh key. the idiomatic way of storing non-default ssh keys is in the location `~/.ssh/key_name`. "ssh_key_file" can be specified as `key_name`, for keys in the default location, or as a relative or absolute custom location eg. `/other_keys/.ssh/nym1` or `../.ssh/nym1`. BREAKING CHANGE: in nostr git url nym1@ssh/npub123/identifer, nym1 is now treated as ssh key file location rather than a ssh user. it can be specified as a file within `~/.ssh` eg `~/.ssh/nym1` or a full or relative path.

feat(send): add `merge-base` tag to PR (Update)

2025-10-17T09:20:43+00:00

following its inclusion in the NIP-34 spec

feat(remote): use push PR non-interactive fallback

2025-09-04T11:09:06+00:00

move the PR push code in 'ngit send' into lib. reuse the non-interactive fallbacks in git-remote-nostr

fix(send): refs not confirmed are usually accepted

2025-08-07T16:49:02+00:00

having implemented 3b5c48f5a2a4b9be5d14baa8f5e801fefd5c1166, a ref pushed to refs/nostr/ on a github repo was accepted but was not confirmed

fix(send):server not confirming acceptance

2025-08-07T16:40:33+00:00

don't treat this as accepted

fix(send): push PR refs to non-grasp servers

2025-08-07T16:40:33+00:00

attempt to use a range of protocols instead of unath http