npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/bin, branch v1.5.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.5.02024-09-18T11:13:26+00:00fix(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
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
refactor(remote): `push` report to match `fetch`2024-09-17T10:40:56+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-17T10:40:56+00:00urn:sha1:12fb184cd1a875704d4f187531aa1638513a3dab
use the same approach taken with reporting remote status in `push`
as is used in `fetch`
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