npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests/git_remote_nostr/push.rs, 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-05T20:30:59+00:00chore: 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
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.
feat(push): send fast-forward merge status event2024-12-06T22:16:44+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-06T22:16:44+00:00urn:sha1:f0d0e1ba1cba11d3a98a5ab0c7f1dc72b6bc4e17
when a proposal was merged using fast-forward status rather than
by creating a three way merge commit.
if there are multiple revisions, the first one that contains merged
proposal tip will be referenced.
if there are multiple proposals that contain one of the commits,
they will all be marked as merged.
the nip needs to be updated as there is no single `merge-commit-id`
so that tag needs to support multiple values
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
chore: bump rust-nostr v0.352024-09-25T13:37:17+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-25T13:37:17+00:00urn:sha1:d6faad17e814d252a72e3aca39a4b3898382bab9
bump all rust-nostr packages
fix(remote): enable login through remote helper2024-09-23T13:13:28+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-23T12:55:00+00:00urn:sha1:0acc9768c2aff4bf4495c89698f29b56dae2f4b4
originally this was disabled because there was a concern that it
would effect the operation of the remote helper due as it prints
to stdout.
it now only writes to stderr.