Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.6.1 2024-12-20T08:07:22+00:00 2024-12-20T08:07:22+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-12-20T08:07:22+00:00 urn:sha1:8cc4a21061433c9a29e36c4f33e4d84bea1defee simplify to allow the removal of warning: `#[allow(clippy::too_many_arguments)]` 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-16T08:55:50+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-12-16T07:58:54+00:00 urn:sha1:5fe839e2bf8ceb2931c1984efb2d956980431203 update nix dependancies to latest version using default update options fix warning related to idomatic patterns 2024-12-12T07:33:15+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-12-12T07:33:15+00:00 urn:sha1:2b49a548169bf9bc3a3ef667a7e952e31e878bab enable nostr git url format alongside and format Merge branch 'pr/nip05-lez(ff1845c0)' 2024-12-10T12:12:14+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-12-10T12:12:14+00:00 urn:sha1:36eb9395567dc0022b1700ec9cda1389baf22476 prioritise using nip05 nostr url format when the nip05, public key mapping is stored in the (usually local) git config. 2024-12-10T11:55:01+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-12-09T09:34:08+00:00 urn:sha1:6d3a4eb870cd344b11ccda13e1339584ed4e4d17 replace `NostrUrlDecoded::from_str` with `NostrUrlDecoded::parse_and_resolve` store nip05 pubkey mapping in git cache 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-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-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.