Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.3-beta1 2024-07-02T07:54:55+00:00 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 2024-04-22T08:29:18+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-04-22T08:29:18+00:00 urn:sha1:6bfd8b0ddec7f8f4c24a97d357de9acd615b0b17 after a new root proposal has been sent link directly to gitworkshop.dev as well as njump.me until gitworkshop is added to njump 2024-03-22T07:19:49+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-03-22T07:19:49+00:00 urn:sha1:ec1d5ca85891ddb083fb2c0e484d5ebf0be9d13f update dependancies to latest version stated in cargo.toml 2024-03-08T14:39:21+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-03-08T14:37:56+00:00 urn:sha1:6b3aecbcbde669859533716225e9c3bbfd2023b2 when since_or_range isn't specified adds resilience as assuming master..HEAD can cause some issues eg when master is not up-to-date with origin/master 2024-03-04T10:54:38+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-03-04T10:54:38+00:00 urn:sha1:b02b4754c027bd751825c8e3b96766a5898187b1 resolve a long standing test issue where failures to output the correct message in the cli would result in the test never ending rather than failing the many test cases updated in this change are to ensure failures are caught rather than ignored some of them are just refactored to remove calling an extra function, which is no longer needed note: this doesn't fix the intermittent issue, most commonly experienced under the nix configuration, where tests that should pass occationally never end preventing the rest of the suite from running 2024-03-01T14:49:48+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-03-01T14:49:48+00:00 urn:sha1:8519dc4a10d47747e6df3f47e25c36bf16befe00 refer to a single patch as patch rather than patches