npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/lib/git/nostr_url.rs, branch v2.2.3Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.2.32025-11-18T11:02:39+00:00test: nostr git url with path2025-11-18T11:02:39+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-18T11:02:39+00:00urn:sha1:3cf8621541b81ec654d5af9bde8297be1916c5fc
add additional test to cover this scenario
chore: cargo update2025-10-17T14:16:03+00:00DanConwayDevDanConwayDev@protonmail.com2025-10-17T14:02:53+00:00urn:sha1:709946c1b49114b71d3080bb8d97e63525f40fd9
update patches ahead of wider upgrade. clippy required some autofixes
feat!(nostr_url): replace user with ssh_key_file2025-10-17T11:18:24+00:00DanConwayDevDanConwayDev@protonmail.com2025-01-16T09:23:05+00:00urn:sha1:b126e5b7acfce55bd101b06cb5baf7f251cd0fda
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.
fix: nip05 breaking changes in rust-nostr2025-07-31T11:35:11+00:00DanConwayDevDanConwayDev@protonmail.com2025-07-31T11:35:11+00:00urn:sha1:9d4adb9afd591ccef8827902034378acd700c6f8
as its now 'bring your own transport'
chore: bump rust-nostr v0.432025-07-31T11:02:08+00:00DanConwayDevDanConwayDev@protonmail.com2025-07-31T11:02:08+00:00urn:sha1:8fe7737a491d6056d6e865bfdecd02e3dda3e8f5
with trival breaking changes. nip05 changes will
be done seperately.
chore: nix flake update2025-07-16T09:39:35+00:00DanConwayDevDanConwayDev@protonmail.com2025-07-16T09:10:41+00:00urn:sha1:092b9606ff2b721d858a5c7b2b27a2f9942b4bc4
required running:
`cargo fix --allow-dirty --allow-staged`
`cargo clippy --fix --allow-dirty -- -D warnings`
to fix problems
and then manually fixing some too
fix(clone_url): fix custom ports2025-05-06T09:51:23+00:00DanConwayDevDanConwayDev@protonmail.com2025-05-06T09:42:02+00:00urn:sha1:b2df89a1f57c136d710962439a86e90fa5249400
only use custom port on specified protocol (ie. http, https or ssh)
ignore custom port on when trying other protocols
specify `ssh://` prefix when using custom port as otherwise it can
be ignored
chore: nix flake update2025-05-05T20:30:59+00:00DanConwayDevDanConwayDev@protonmail.com2025-05-02T13:37:14+00:00urn:sha1:a744f4aae9ffee9dd246090bef486b09433778d0
update nix dependancies to latest version using default update options
run `cargo clippy --fix` and `cargo fmt` to fix new clippy errors
chore: bump rust-nostr v0.37 ~> v0.402025-04-01T13:35:50+00:00DanConwayDevDanConwayDev@protonmail.com2025-04-01T13:31:34+00:00urn:sha1:948fe972eb2bddf187b79f2673a091b6331cfd90
and fix all of the breaking changes
refactor: use nostr url from repo_ref2024-12-20T08:07:22+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-20T08:07:22+00:00urn:sha1:8cc4a21061433c9a29e36c4f33e4d84bea1defee
simplify to allow the removal of warning:
`#[allow(clippy::too_many_arguments)]`