npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests/send.rs, branch v1.3.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.3.12024-07-24T15:37:10+00:00refactor: use nip34 kinds from rust-nostr2024-07-24T15:37:10+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-24T15:37:10+00:00urn:sha1:8638b321fdff94d034ec912ecd0910b6f564ff04
instead of Kind::Custom(u16) as v33 of rust-nostr introduced them
feat: intergrate `fetch` into `send`2024-07-19T19:38:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-19T19:38:00+00:00urn:sha1:ab1214060a7a2d55068a7ccc9c7f6a04fd7d5aa2
reworking the tests and test suite as appropriate
feat(login): use fetch to get user profile2024-07-17T09:53:20+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-17T09:53:20+00:00urn: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
feat(send): tag each maintainer's repo event2024-07-02T07:54:55+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-02T07:54:55+00:00urn: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
feat(login): store in git config and use cache2024-06-24T08:39:18+00:00DanConwayDevDanConwayDev@protonmail.com2024-06-24T08:39:18+00:00urn: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
chore: bump rust-nostr to v0.32.02024-06-13T08:09:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-06-11T15:21:44+00:00urn: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
feat: add NIP-31 alt tags2024-05-23T13:44:39+00:00DanConwayDevDanConwayDev@protonmail.com2024-05-23T13:44:39+00:00urn:sha1:3b4f0b0eee124133b641d6770704c368712f3dff
to repo announcements, patches and cover letters
feat(send): `in-reply-to` tags npubs and events2024-05-07T08:10:33+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-22T06:26:15+00:00urn: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
feat(send): print link to proposal root2024-04-22T08:29:18+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-22T08:29:18+00:00urn: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
chore: cargo update2024-03-22T07:19:49+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-22T07:19:49+00:00urn:sha1:ec1d5ca85891ddb083fb2c0e484d5ebf0be9d13f
update dependancies to latest version stated in cargo.toml