Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.6.0 2024-12-16T09:46:30+00:00 2024-12-16T09:46:30+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-12-16T09:00:46+00:00 urn: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` 2024-12-09T15:35:18+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-12-09T15:35:18+00:00 urn:sha1:d8f4f7641312bff32f772cbc070b3f99ced0c8fe get the latest user relay list before pushing patches and repo announcement events 2024-12-05T12:13:02+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-12-05T12:13:02+00:00 urn:sha1:c6fef5613fc64037e591a6515c025d5ed559915c when nostr address is unknown and user is prompted, validate that a the entered repo exists (there are events related to it) before proceeding 2024-12-04T15:36:17+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-12-04T15:36:17+00:00 urn:sha1:e00f712fb09d2a55fbfd36696f3725bc44c140f5 git-remote-nostr is always called with a nostr remote that specifies a single repository coordinate whereas `ngit` commands need to discover this. this change moves from getting this value from the following places in priority order: 1. git config item `nostr.repo` 2. first nostr remote discovered 2. maintainers.yaml 3. prompt the user to: 1. nostr remote - if multiple, prompt the user to select 2. git config item `nostr.repo` 3. maintainers.yaml - removing the legacy format 4. prompt the user - now with support for nostr remote format 2024-11-27T17:08:25+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-11-27T17:08:25+00:00 urn:sha1:83448a99aaf18c7a045a081c5de0c22bc4a83de1 use RelayUrl in repo_ref which I had resisted as it mutates relay urls when printed to append a slash 2024-11-26T12:26:47+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-11-26T07:48:30+00:00 urn: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 2024-11-21T16:53:17+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-11-21T16:53:17+00:00 urn: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 2024-09-25T13:37:17+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-09-25T13:37:17+00:00 urn:sha1:d6faad17e814d252a72e3aca39a4b3898382bab9 bump all rust-nostr packages 2024-09-04T13:23:54+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-09-04T10:32:05+00:00 urn:sha1:771f944af447c202eba045936a36dee71ab797ac move some functions out of ngit and into lib/mod and lib/git_events remove MockConnect from binaries so it is only used in the library. this was done: * mainly because automocks were not being imported from lib into each binary * but also because the these functions were being tested with MockConnect 2024-09-04T12:30:59+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-09-04T07:04:48+00:00 urn:sha1:949c6459aa7683453a7160423b689ceadb08954b the make the code more readable this commit just moves the files, the next commit should fix the imports