Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.6.2 2024-12-16T16:50:39+00:00 2024-12-16T16:50:39+00:00 Laszlo Megyer lez@github.com 2024-12-16T10:38:06+00:00 urn: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. 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-12T11:32:48+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-12-12T11:31:51+00:00 urn:sha1:6f45aa9937602f3d03cd83cfb5fb3c541fac4adf prevent a panic when tags are of an unexpect length 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-03T15:29:06+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-12-03T15:29:06+00:00 urn: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. 2024-11-28T15:08:39+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-11-28T15:07:02+00:00 urn:sha1:5dbac4d643f4dc5110bf9971e29598dfc30d75f0 as default instead of user write or none 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-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