npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/lib/client.rs, 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-16T09:46:30+00:00chore: 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
feat: only print awaiting signer with nip462024-11-27T17:28:29+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-27T17:28:29+00:00urn:sha1:e40e96a4364464b4e88d3db7a81485b978b57c07
using the backend feature I requested for rust-nostr
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
refactor: err msgs 'cannot' > 'failed to'2024-11-26T12:26:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-26T07:48:30+00:00urn:sha1:a0593e3aa9b19b9ca3c3881cbe0d9d207fe46d2c
in nearly all cases 'cannot' was used when an action was tried and
failed. 'failed to' is strictly better because:
* just because the action didn't work that time doesnt mean it
cannot work
* it is better at drawing the users attention to a problem
feat(login): overhaul login experience2024-11-21T16:53:17+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-21T16:53:17+00:00urn:sha1:f79014235e85554e3661b3f2a02b8fa88bc192ff
* simplify login menu, making it more accessable to newcomers and
easier to select remote signer options
* enable `ngit login` to work from anywhere (not just a git repo)
* assume fresh login details saved to global git config but fallback
to local repository
* maintain local repository login via `ngit login --local`
* maintain login via CLI arguments eg `ngit send --nsec nsec123`
* nudge users to remember nsec when pasting in ncryptsec for a
better UX, whilst maintaining the option to be prompted for
password everytime
* create placeholder menu items for help menu and create account