npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests, branch v1.2.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.2.12024-05-07T08:10:33+00:00feat(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
test: fix intermittent test failures2024-03-28T11:56:12+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-28T08:26:19+00:00urn:sha1:bc1e9e7ff8d2c3747a7dbc3b649930ac5bc6425d
caused by test proposals with the same timestamp
listed in an inconsistant list order;
by ensuring test proposals have a different timestamps
replace blocking client in tests with async2024-03-27T17:18:54+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-22T15:51:42+00:00urn:sha1:71606283bf21f0fb4931850cd69d97344dca521e
as it has been removed from nostr_sdk
update tag generation2024-03-25T11:46:23+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-22T15:51:40+00:00urn:sha1:49bc478fffc63a3cad0be194c6c45a868e432691
to reflect changes in rust-nostr
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
feat(send): select commits from a list2024-03-08T14:39:21+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-08T14:37:56+00:00urn: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
test: ensure failed tests timeout2024-03-04T10:54:38+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-04T10:54:38+00:00urn: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
feat(send): fix grammar in cli output2024-03-01T14:49:48+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-01T14:49:48+00:00urn:sha1:8519dc4a10d47747e6df3f47e25c36bf16befe00
refer to a single patch as patch rather than patches
feat(send): when on main default to sending 1 patch2024-03-01T14:49:13+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-01T14:49:13+00:00urn:sha1:445eea13d987b345535fd4fa56486ff334bbd351
based on feedback from santos:
nostr:31c085a584cbd30f71a44a70eaf828c2c8c5f6e3efb7942547edb37cf4a632cf