Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.2.0 2024-09-09T08:40:19+00:00 2024-09-09T08:40:19+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-09-09T08:40:06+00:00 urn:sha1:9a9b13a11868fe58fa0390938a39483bf1f3cc9a in prep for splitting git_remote_nostr tests 2024-08-28T15:42:53+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-08-28T13:20:34+00:00 urn:sha1:a5216602749bff55c2773acce098c91942cd3920 bump all rust-nostr packages I'm not sure I'm completely happy with allowing mutable_key_type but it is just run inside tests it appears that Event didn't have the Copy trait in v0.33.0 so I'm not sure why this warning suddenly appeared the timeout of client.get_events_of needed to be doubled which could indicate that an ineffiency has been introduced in v0.34.0 the primary motivation for upgrading now was to get this fix: nostr:nevent1qqsffl2ld678pjj77rh9k2g4edljmxdu6ew4lvgnglxv7jhu3ru8vvcpp4mhxue69uhkummn9ekx7mqzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6rm2ucm as I suspect it is also effecting other repositories eg nostr-profile-manager 2024-07-24T15:37:10+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-07-24T15:37:10+00:00 urn:sha1:8638b321fdff94d034ec912ecd0910b6f564ff04 instead of Kind::Custom(u16) as v33 of rust-nostr introduced them 2024-07-19T19:38:00+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-07-19T19:38:00+00:00 urn:sha1:ab1214060a7a2d55068a7ccc9c7f6a04fd7d5aa2 reworking the tests and test suite as appropriate 2024-07-17T09:53:20+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-07-17T09:53:20+00:00 urn:sha1:43a445963968dac7da190b56f7c89ac0ff1f6abd fetch automatically gets updates to logged in user profile / relays fetching without specifying repo pointers will just fetch user profiles so that can be used during login, if user profile isn't in cache login now uses fetch 2024-07-02T07:54:55+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-07-02T07:54:55+00:00 urn:sha1:58cc0a9662e1bd087c2910eb15aa7568f088bba5 instead of just tagging the first maintainer's repo event and each maintainer with a p tag This allows for easier discoverability of the proposal when: * the first maintainer hasn't issued a repo event * the maintainers change over time and the single tagged repo event is no listed as a maintainer in anyone elses repo event 2024-06-24T08:39:18+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-06-24T08:39:18+00:00 urn:sha1:173ab188b326fbe78cfba4ab455a74619f4556bb replace ngit yaml file config with: * nsec / ncryptsec / npub in git config in nostr.* namespace * sql database cache for metadata and relay events allow different logins to be used for different git repositories by storing login in local git config 2024-06-13T08:09:00+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-06-11T15:21:44+00:00 urn:sha1:f1b3fcc40ab666d8def97096d1942c274da9b279 both nostr and nostr-sdk packages and also in test_utils fix the many breaking changes fix: ignore trailing slash when depuplicate relays for send events. this was picked up as TagStandard::RelayMetadata has started adding a traling slash. refactor cli output test function `expect_send_with_progress` so that relays can succeed / fail in a random order 2024-05-23T13:44:39+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-05-23T13:44:39+00:00 urn:sha1:3b4f0b0eee124133b641d6770704c368712f3dff to repo announcements, patches and cover letters 2024-05-07T08:10:33+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-04-22T06:26:15+00:00 urn:sha1:10498b953d36304b441fcb162155c2487046206f in addition to being used to create a new proposal revision, in-reply-to can now be used to reference other events and npubs. for example an issues or kind 1 threads where the proposal is relevant the proposal will only be marked as a revision if the first parameter is a reference to an existing proposal root