npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/lib/client.rs, branch v1.6.3Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.6.32025-05-05T20:30:59+00:00chore: 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
feat(send): add description to event signing process2025-04-03T16:13:50+00:00DanConwayDevDanConwayDev@protonmail.com2025-04-03T16:13:50+00:00urn:sha1:29688c2cfe32a27dd9faabd66691f6db1cd4818a
resolving
nostr:note1qu8le4a8qz9hhxy6q85txejcq0kln0r3s9vdtwrhtqwvauc6nxuqn3fj0z
so it doesnt appear frozen when there are lots of events being signed
by a remote signer
fix: publish error prefix regression2025-04-02T14:56:03+00:00DanConwayDevDanConwayDev@protonmail.com2025-04-02T14:56:03+00:00urn:sha1:95cd190dd2d008f96bcf5c27a0fc4aa0d073c666
introduced by rust-nostr v0.40 from v0.37
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
chore: bump nix flake rust nightly `fmt` overlay2024-12-16T09:46:30+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-16T09:00:46+00:00urn:sha1:4ee83e2fe5335a8afd78439c35f029c4a472e797
update the rust nightly `fmt` overlay which needs to be pinned
to a specific version (this case by date)
update formatting in main files via `cargo fmt`
refactor: limit fetch to 1 trusted coordinate2024-12-03T15:29:06+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-03T15:29:06+00:00urn:sha1:d2478dbca6c5d3f61331ceabe20c6d9315cd6840
previously fetch supported fetching multiple trusted coordinates at
once. The additional complexity trade off isn't worth it.
It will still fetch events related to the coordinates of maintainers
that the trusted maintainer lists.
A scenario where there might be multiple trusted coordinates is
where a large repo is split into multiple nostr repos to manage
pull requests and issues in seperate sub-units. I might therefore
have different remotes that target different identifiers.
There also might be different set of maintainers groups that are
have different views on the latest state of the same codebase and
they haven't split off into using different identifiers.
Its simplier ngit to fetch these different nostr repos independantly
when requested. git-remote-nostr will do this automatically as it
works through remotes but for ngit cmds a further change is required
so `get_repo_coordinates` and `try_and_get_repo_coordinates` prompts
to select the desired one.
fix: repo_ref 'not found' err suggest `ngit init'2024-12-02T07:20:05+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-02T07:20:05+00:00urn:sha1:a6a1eebda0ab5e8b34e97799ff7b57ef194261c7
if the nostr remote was created by the maintainer before
`ngit init` was ran.
the error is more likely to occur when a user clones a repo using
the nostr remote whist the relay in the hint is down and the fallback
relays dont have the announcement. or if the user is offline when
they clone.
fix(repo_ref): clarify no repo event err msg2024-12-02T06:50:19+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-02T06:50:19+00:00urn:sha1:d482eb8f33b571c56ca3e3fa4ae05d6cd8069569
as there might be a repo event but we couldn't find it
feat(init): set remote `origin`2024-11-29T16:57:46+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-29T16:09:38+00:00urn:sha1:8c763d0483309c85a32a7f4a20ba0279083ee40f
check whether remote `origin` is nostr url and if not attempt
to set it.
refactor: remove fufilled comment2024-11-28T07:21:07+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-28T07:21:07+00:00urn:sha1:7e2f354d6fb07b1a9f1bb7bc50287972deec2b83
as the feature is implmeneted