npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/bin/git_remote_nostr, branch v1.5.2Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.5.22024-09-24T18:48:11+00:00feat(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): 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.
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.
feat(remote): add send events status reporting2024-09-20T10:30:11+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-20T10:30:11+00:00urn:sha1:667cc246ffb0a6410ff2d445d3e3ba522c6a2c4e
to both tell users where events have been sent / failed to be sent
and to provide a status update so the user doesn't think its crashed
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): push report copy2024-09-18T08:36:06+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-18T08:31:52+00:00urn:sha1:47f4bf046eb0cb7f45fe2f26359a177ef40cd68e
improved for push to each git server. report now reflects new
branch / tag, delete branch / tag and force flag.
fix(remote): push don't report on writing 0 obj2024-09-17T13:05:59+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-17T13:05:59+00:00urn:sha1:197fc5a285bb07b7853dd2004bb5666d4527eb11
in the TUI as its not useful
fix(remote): push reporting copy2024-09-17T12:36:45+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-17T12:36:45+00:00urn:sha1:2163e0a01f934692c8967a11eb9828fd70f7d03d
ensure commit id from and two are the correct way around
fix(remote): `push` exit protocol loop on success2024-09-17T12:32:06+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-17T12:32:06+00:00urn:sha1:31f8cb32c6b6cec266f6f97ceefe666addc5069d
so that other protocols are not tried after push was successful