npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/test_utils/src/lib.rs, branch v1.7.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/atom?h=v1.7.12025-06-02T06:51:22+00:00tests: fix tests by adding maintainer ann event2025-06-02T06:51:22+00:00DanConwayDevDanConwayDev@protonmail.com2025-06-02T06:51:22+00:00urn:sha1:4625958aa51d3bfc67f89e39fa28b843a1f0ac8e
to comply with changes in 5f45edbebe310decb06f955d95665a6ad387c6cb
test: fix test func get_proposal_branch_name2025-04-02T11:10:35+00:00DanConwayDevDanConwayDev@protonmail.com2025-04-02T11:10:35+00:00urn:sha1:93dc41ac454adc403c32009fc501cd73d82fc80c
it was not correctly checking for "revision-root" tag
rust-nostr v0.40 changed the sorting order so that the revision-root
may be returned first causing intermitant test failures
chore: bump rust-nostr v0.37 ~> v0.402025-04-01T13:35:50+00:00DanConwayDevDanConwayDev@protonmail.com2025-04-01T13:31:34+00:00urn:sha1:948fe972eb2bddf187b79f2673a091b6331cfd90
and fix all of the breaking changes
chore: bump nix flake rust nightly `fmt` overlay2024-12-16T09:46:30+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-16T09:00:46+00:00urn:sha1:4ee83e2fe5335a8afd78439c35f029c4a472e797
update the rust nightly `fmt` overlay which needs to be pinned
to a specific version (this case by date)
update formatting in main files via `cargo fmt`
test(push): merge event for applied commits2024-12-13T12:37:22+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-13T12:02:15+00:00urn:sha1:ee0e048ed9c244449ffb12284e444933eb67e118
publish a merge event when the commit author signature and timestamp
match patches within an open proposal
test: deterministic commit timestamps in test PRs2024-12-13T12:37:20+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-12T15:19:40+00:00urn:sha1:f294a249307accc0f173917989ce27c27f0c6792
now that the remote helper uses the commit author timestamp to
determine if commit was applied from a proposal, the timestamps
in the test proposal can no longer be identical.
this makes them deterministically different based on the file name
chore: bump rust-nosrt v0.37.02024-11-27T17:08:25+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-27T17:08:25+00:00urn:sha1:83448a99aaf18c7a045a081c5de0c22bc4a83de1
use RelayUrl in repo_ref which I had resisted as it mutates relay
urls when printed to append a slash
test(login): update `ngit login` test2024-11-26T16:28:09+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-26T16:28:09+00:00urn:sha1:bdf71cb3d5a5ff8399c10c8d2492d3dd01c5fa33
to reflect the new interface and testing only nsec login
refactor: err msgs 'cannot' > 'failed to'2024-11-26T12:26:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-26T07:48:30+00:00urn:sha1:a0593e3aa9b19b9ca3c3881cbe0d9d207fe46d2c
in nearly all cases 'cannot' was used when an action was tried and
failed. 'failed to' is strictly better because:
* just because the action didn't work that time doesnt mean it
cannot work
* it is better at drawing the users attention to a problem
feat(list): report on action selection2024-11-25T16:09:36+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-25T16:09:36+00:00urn:sha1:0c5a3c001ccafd458a9b99b7513a9c8c172a54b2
there was a bug in `Interactor` so that reports were turned off by
default for choices.
This was embodied into the CLI tests but this turns them on in these
scenarios.