npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/src/bin/git_remote_nostr/fetch.rs, branch v1.5.3Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/atom?h=v1.5.32024-09-25T13:37:17+00:00chore: 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
feat(login): login via nip46 QR code2024-09-24T18:48:11+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-24T14:03:58+00:00urn:sha1:d01380f7b3efebc9c40a2e71c2ddd635fa936be4
or nostrconnect url string which is a much better UX flow for nip46
fix(remote): add resilience to `prs`2024-09-23T12:36:53+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-23T09:46:26+00:00urn:sha1:2cdbb8c7ac6c98af6e36c4458c08bef2299794e1
make poorly formatted patches fail silently. we stop trusting that the
`commit` tag in the latest patch can be produced by apply the patches.
to achieve this we must recreate the commit during the list command,
which require fetching the parent oids.
support patches without optional `commit` and `parent-commit` tags.
fix(remote): create pr commit error reporting2024-09-18T11:13:26+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-18T11:13:26+00:00urn:sha1:e91f95f0d4577d64e41e3ac1d7ae87035a5f12e0
so it clear which patch is causing issues and it continues to report
the fetch problem to the git client.
we need a better solution it degrades gracefully rather than
stopping the operation.
perhaps list needs to only list PRs which it can create from existing
data objects?
perhaps list also needs fetch objects before fetch is called?
fix(remote): reporter lines on narrow terminals2024-09-18T10:11:41+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-18T10:11:41+00:00urn:sha1:c7838f952f9e32bb871ea6453595b8b14e8fdd3e
remove the correct number of lines when reporter prints to
narrow terminals
feat(remote): store successful protocol in config2024-09-17T12:23:22+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-17T12:23:22+00:00urn:sha1:a4bcaf98cc7a00a71f34ed382dc65414eaec5bff
if another protocol was tried first and failed
fix(remote): `fetch` dont show resolving 0 deltas2024-09-17T06:39:05+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-17T06:39:05+00:00urn:sha1:4f76e3d99ece9f9a15bbb4e6c2c26ccd1ef48900
in progress updates as its not resolving any deltas
fix(remote): fetch report join remote lines2024-09-16T15:26:33+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-16T15:26:33+00:00urn:sha1:ff80e0d444579c72dfab755b98bc79da1b1a4ffe
when they are sent via multiple messages
refactor(remote): add tests to fetch reporting2024-09-16T15:02:52+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-16T15:02:52+00:00urn:sha1:32d427865a59ed245bbf898e6f4a8d5ad1ff1958
and slightly refactor
fix(remote): fetch status reduce line writes2024-09-13T19:40:01+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-13T19:40:01+00:00urn:sha1:d832abb04887ae3ae6e4d88f2915e3ac6a1fcff8
by only removing and rewriting transfer progress