npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests, 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
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
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
test(ngit): no nostr remote, search for repo2024-12-05T12:47:59+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-05T12:47:32+00:00urn:sha1:cabbdea4ae39a57cbff10d24084a888ca9948083
update the tests to reflect the changes in the previous 4 commits
feat(init): set remote `origin`2024-11-29T16:57:46+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-29T16:09:38+00:00urn:sha1:8c763d0483309c85a32a7f4a20ba0279083ee40f
check whether remote `origin` is nostr url and if not attempt
to set it.
test(init): fix cli white space issue2024-11-29T10:21:24+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-29T10:21:24+00:00urn:sha1:cf90fc9be18523b01c50efcfae3afffc93fff599
otherwise the test never ends or fails