npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/lib/login/user.rs, branch v2.3.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.3.02026-02-27T14:24:58+00:00feat: only show login profile search and warnings in verbose mode2026-02-27T14:24:58+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-27T10:23:23+00:00urn:sha1:7b393f2e249e3bda141994d0c67aa9812d87302a
reduces noise in normal usage; messages still appear with -v flag
feat: use fallback relays for bootstrapping only2026-02-11T15:54:51+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-11T09:20:48+00:00urn:sha1:15bf0d0b6befae6c81631c0e5d0dc2947dd3318a
- Add --relay flag to 'ngit account create' allowing users to specify
relay URLs (repeatable). Defaults to relay-default-set when not provided.
- Remove fallback relays from fetch when repo context exists (repo
coordinate provided). Only use them for bootstrapping (profile discovery
with no repo context).
- Remove fallback relays from publish when repo or user relays exist.
Only use them when neither is available (e.g. new account signup).
- Update --customize help text to reflect new relay-default-set behavior.
feat(send): PR fallback to user / custom grasp2025-08-07T16:25:50+00:00DanConwayDevDanConwayDev@protonmail.com2025-08-06T11:52:59+00:00urn:sha1:a9b2ebf8216be34950e54dd9a446dbdc0c9c744a
if use is maintainer, push PR to all repo git servers.
if user has a fork, push to all git servers it lists, and repo
grasp servers.
if user hasn't got a fork but has a user grasp list and pushing
push to repo grasp servers fails, create a personal-fork
automatically at each user grasp server and push there.
fallback to prompting user for either grasp servers or git server
with write permission.
if user provides grasp servers, suggesting adding to user preference
list.
feat(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): 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