npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/lib/login/mod.rs, branch v2.0.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.0.02025-07-16T09:59:20+00:00chore: bump nightly rustfmt2025-07-16T09:59:20+00:00DanConwayDevDanConwayDev@protonmail.com2025-07-16T09:59:20+00:00urn:sha1:ac53bca7e315848864ff9e51703720b5b466bc42
to latest available and apply fmt fixes
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
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: 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: 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): tweak local login wording2024-11-22T17:14:01+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-22T17:14:01+00:00urn:sha1:c6866d621e02205343b175d929785c8a73022806
because a user might be logged in to the same account locally
and globally
feat(login): `ngit login` use cli args2024-11-22T16:28:14+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-22T16:15:57+00:00urn:sha1:737b7c5728d1688ace4d35a016fbdaed5ffc4e79
previously cli args were only used during other commands to bypass
normal login
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
fix: get correct nip46 npub in edge case2024-11-12T11:59:50+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-12T08:06:44+00:00urn:sha1:a94c24b177692b8c719fafdaf2728c723657fd39
when there is an npub listed in git config but login was via direct
cli arguments to the current process, the wrong npub would be used.
this is the case for the ngit_init tests.
this can be more eligantly if rust-nostr NostrConnect::new() were
updated to accept user public key as requested here:
https://gitworkshop.dev/r/naddr1qvzqqqrhnypzq6xcz9jerqgqkldy8lpg7lglcyj4g3nwzy2cs6u70wejdaj7csnjqy88wumn8ghj7mn0wvhxcmmv9uqq5un4wd6z6mn0wd68y2z2qh0/issues/note1qa2pty0mnjhsme3thza24u3nv8u7859fqw2qg6fuyx9w00e2gekqvl3yg9