npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/lib/login, branch v1.6.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.6.02024-12-16T16:50:39+00:00feat(init): default to nip05 git nostr url2024-12-16T16:50:39+00:00Laszlo Megyerlez@github.com2024-12-16T10:38:06+00:00urn:sha1:cc87576cdfdd3aa18df6e94fbfa079d9e4f0241a
If the user has NIP-05 set up in profile, and it resolves at the time
of running `ngit init`, NIP-05 will be used in the nostr remote url.
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`
fix: defend against empty`tags`2024-12-12T11:32:48+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-12T11:31:51+00:00urn:sha1:6f45aa9937602f3d03cd83cfb5fb3c541fac4adf
prevent a panic when tags are of an unexpect length
fix: fetch user relays for `send`,`push` & `init`2024-12-09T15:35:18+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-09T15:35:18+00:00urn:sha1:d8f4f7641312bff32f772cbc070b3f99ced0c8fe
get the latest user relay list before pushing patches and repo
announcement events
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.
feat(init): user read or fallback relays2024-11-28T15:08:39+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-28T15:07:02+00:00urn:sha1:5dbac4d643f4dc5110bf9971e29598dfc30d75f0
as default instead of user write or none
feat(login): contact remote signer when needed2024-11-27T17:20:28+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-27T17:20:28+00:00urn:sha1:75cd323e2481502671aa1f62b28875d95f9863c3
for existing login, the remote signer should only be called when an
event needs to be signed. This might be a AUTH event so we still
need to call it during read scenarios.
a feature was added to rust-nostr to enable this.
chore: bump rust-nosrt v0.37.02024-11-27T17:08:25+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-27T17:08:25+00:00urn:sha1:83448a99aaf18c7a045a081c5de0c22bc4a83de1
use RelayUrl in repo_ref which I had resisted as it mutates relay
urls when printed to append a slash
fix: add white border to qr codes2024-11-27T07:56:34+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-27T07:56:34+00:00urn:sha1:242601c972b7186ad380d301b7c12ce9d19aa959
to improve machine readability
feat(export-keys): to use in other clients2024-11-27T07:41:25+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-27T07:41:25+00:00urn:sha1:c92e252adc9990fa4d147bad0a8bccafc19dfbb8
as part of the easy on-boaridng flow