npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/test_utils/src/lib.rs, 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
rename from_sk_str -> from_str2024-03-22T15:51:34+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-22T15:51:34+00:00urn:sha1:0d7a8383d7d54e64bb0e1d5f4e06110c1e6a818b
to reflect new name in rust-nostr
chore: nix flake update2024-03-22T15:45:04+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-22T07:35:24+00:00urn:sha1:91a68de459b7d22a8dfb8a324e43740fca3e0a35
update nix dependancies to latest version using default update options
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
refactor: improve rexpect error message2024-03-04T12:19:14+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-04T12:19:14+00:00urn:sha1:050d9978193d6e0802d045c2b6897117a5a90b61
to enable better debugging
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
build: added to gitignore2024-02-29T13:09:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-29T13:09:47+00:00urn:sha1:df239f3536b08d295017f94d0a93c1c00a5039bc
so temporarly created test directories and files are ignored
feat(list): set checkout branch as default choice2024-02-20T16:48:48+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-20T16:22:10+00:00urn:sha1:141ebf0cc0c6cfea640debc9b9073303509a8bc7
instead of no default. note: I spent hours trying to get
CliTester to support default choices and gave up.
I have a stashed the attempt and am moving on...
feat!: nip34 set pr kind to patch kind2024-02-13T16:25:19+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-13T16:25:19+00:00urn:sha1:1022344a0529b5f6b50f35d3030a528a1a5c6f91
this enables consistancy of display with simple clients that are just taking
the output of `git format-patch`
test: fix backtrace display2024-02-13T15:55:58+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-13T15:34:21+00:00urn:sha1:2d6800b3aacc3b8ea223fc92ae7db1e2ae868109
between 5 Feb 2024 and 13 Feb 2024 backtrace began activiating in
`nix-shell` and ci during integration tests when rexpect.
this caused some error tests to fail / hang
it was not activating in the `nix-shell` when the cli
was called seperately
setting the `RUST_BACKTRACE=0` in the rexpect config surpresses
the backtrace as desired