npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/test_utils/src/lib.rs, branch v1.6.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.6.12024-12-16T09:46:30+00:00chore: 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.
est(list): fix getting pr branch name2024-11-12T11:59:49+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-11T20:30:08+00:00urn:sha1:98775a626b7a956378b8fa26f60a869d27068538
rust-nostr must have changes the order in which it
returns elements.
a proper fix would be to work out why there are duplicates!
chore: bump rust-nostr v0.362024-11-11T13:08:35+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-11T13:08:35+00:00urn:sha1:30f1a3efa9265b1403a7aa68fffbd65291face3d
bump all rust-nostr packages to latest issued version.
there have been some breaking changes to nip46 and this applies
these changes.
chore: bump rust-nostr to patch near v0.36.02024-10-28T15:41:14+00:00DanConwayDevDanConwayDev@protonmail.com2024-10-28T15:41:14+00:00urn:sha1:ae87aedae9696f4c855ac3dc47e61faec9d07c15
bump all rust-nostr packages
refactoring code based on breaking changes
upgrading to patched version to address signer issue:
nostr:nevent1qvzqqqqqqypzq6xcz9jerqgqkldy8lpg7lglcyj4g3nwzy2cs6u70wejdaj7csnjqy88wumn8ghj7mn0wvhxcmmv9uqzpsw5ph8le2n2kh6uchftawt74hddazk9tp7wjmz967y2l0uva5rc7hsstq