npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests, branch v1.6.2Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.6.22025-05-06T13:00:29+00:00chore: update git2 ~> v0.20.22025-05-06T13:00:29+00:00DanConwayDevDanConwayDev@protonmail.com2025-05-06T12:51:26+00:00urn:sha1:c19f173199b6beebf078a9e5c54014dbef85aa82
we have had some bugs related to git2 so moving to the latest version
chore: nix flake update2025-05-05T20:30:59+00:00DanConwayDevDanConwayDev@protonmail.com2025-05-02T13:37:14+00:00urn:sha1:a744f4aae9ffee9dd246090bef486b09433778d0
update nix dependancies to latest version using default update options
run `cargo clippy --fix` and `cargo fmt` to fix new clippy errors
test: patches shouldn't `p` tag author2025-04-02T09:44:17+00:00DanConwayDevDanConwayDev@protonmail.com2025-04-02T09:44:17+00:00urn:sha1:e7a3ac18cc16d8775230598f955468600b6dc32b
rust-nostr upgrade to v0.40 removed this `p` tag
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
test(push): ff merge commit tag `merge-commit-id`2024-12-12T13:53:57+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-12T13:53:57+00:00urn:sha1:aefaadcdf8891d8fb235f87e14c498016b3fbcef
allow any order of the commit ids
fix(push): three-way `merge-commit-id` `tag`2024-12-12T12:49:34+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-12T12:49:34+00:00urn:sha1:5a4402ce83094d797f7c2c8780dbc35e0d738dec
should alway list only the three-way merge commit id.
fix: fetch user relays for `send`,`push` & `init`2024-12-09T15:35:18+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-09T15:35:18+00:00urn:sha1:d8f4f7641312bff32f772cbc070b3f99ced0c8fe
get the latest user relay list before pushing patches and repo
announcement events