npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/sub_commands/send.rs, branch v1.3.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.3.02024-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(push): `--force` tries non-interactively2024-07-24T14:25:43+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-24T14:01:49+00:00urn:sha1:9078d0d80d1fe98ec9e6cd116c3dd70b6e0dd55a
if branch is ahead of main or master
feat(list): unique proposal branch names2024-07-23T15:36:06+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-23T15:36:06+00:00urn:sha1:b67376ff54abeab31422921ba5f4883d5d3dccdb
to prevent accidental name conflicts. also moved to prs/* namespace
`pull` and `push` integration tests are intermitantly failing to end
at least for `push` they work when run individually but not
when run together
chore: bump rust-nostr to v0.33.02024-07-22T14:26:44+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-22T14:26:44+00:00urn:sha1:0762d44a9ec3d8a5477e171933428cd9749e0659
bump all rust-nostr packages
move from using patched nip46 nip05 function to profile function in v33
fix send_events_to error message
feat: save created events to cache2024-07-19T21:10:23+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-19T21:10:23+00:00urn:sha1:29a093993ce7d0210ac39ceb1a25acc9350492e7
as soon as they are successfully sent to at least one relay
feat: integrate `fetch` into `push`2024-07-19T20:20:53+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-19T20:20:53+00:00urn:sha1:8531328558c7f5870be3571f63a952743eb0b9e6
as part of a project to use `fetch` and the stored cache everywhere
feat(send): add relay hints to link2024-07-19T19:47:30+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-19T19:47:30+00:00urn:sha1:fca1d193a46eba17255b5372adffac2396e48c04
to proposal which is displayed at the end of the functon
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(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): login with nip46 remote signer2024-06-28T14:16:43+00:00DanConwayDevDanConwayDev@protonmail.com2024-06-28T14:16:43+00:00urn:sha1:a82546b70303000b4fc053a1ee21d3d8c7d6ad66
and save details in git config