npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/lib/list.rs, branch v2.2.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.2.12026-02-16T15:13:51+00:00test: fix list reporter under test conditions2026-02-16T15:13:51+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-16T15:13:51+00:00urn:sha1:d0dfadf9fff8e81f11677dba6920b885c818c4d4
this took a lot of investigation to work out why this was failing
fix: reporter git server non-verbose2026-02-16T13:02:50+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-16T13:02:50+00:00urn:sha1:0723d3d350ffb1dc78161565dcc5605c95b1c051
hide details in non-verbose mode
feat: add spinner for git fetch in non-verbose mode2026-02-13T10:51:25+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-13T10:51:25+00:00urn:sha1:40b439ae4d69b858274be51dd5af513c3b4f46f0
Shows a progress spinner when fetching from git remotes in non-verbose mode.
Suppresses git fetch output and listing messages when not in verbose mode.
Uses NGITTEST environment variable for test timeouts.
fix: clear progress reporters on successful completion2026-02-13T08:10:50+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-13T08:10:50+00:00urn:sha1:64f1cf4f8e021f52f8e7df75e62f10d32d9fa101
Progress reporters were not being cleared after successful operations,
leaving progress bars visible in the terminal output. Now they are
properly cleared when all operations complete without errors.
fix: cli output dim coloring2025-11-13T22:11:17+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-13T21:11:05+00:00urn:sha1:cfa26fa55b72783ea64bbd39d5d0fbdf94370b1b
so that relay/git servers appear dim when fetch action is complete
feat(list): make list async and include sync report inline2025-11-13T22:08:56+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-13T17:18:35+00:00urn:sha1:82c7a95f6e9aa266d2f0d2035a0ce4f1715b62ad
copy relay fetching approach to async and reporting
refactor: simplify get_short_git_server_name2025-11-13T14:55:50+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-11T12:30:00+00:00urn:sha1:ebab8d2aa487d1814e802c5a51b19d4bb1592e01
so it doesnt use the git_repo
fix: out of sync grasp server cli output2025-11-13T14:49:00+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-11T08:31:46+00:00urn:sha1:65f3bd360c065aca493eddf7eb5d3d8191a84b56
so it shows a summary rather than a lot of lines of issues
fix: cli output line deletion during fetch2025-11-13T14:40:09+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-11T07:21:08+00:00urn:sha1:52370f542dad87ab029a5d701cc46658d5aef91b
also reduce the clutter in the cli output for grasp servers.
feat!(nostr_url): replace user with ssh_key_file2025-10-17T11:18:24+00:00DanConwayDevDanConwayDev@protonmail.com2025-01-16T09:23:05+00:00urn:sha1:b126e5b7acfce55bd101b06cb5baf7f251cd0fda
replaces the "user" in the nostr_url format with
"ssh_key_file", to support the original intent, which was to allow
users to specify different authentication credentials.
most git servers always expect the ssh user to be 'git'.
the idiumatic way of specifying logging in as a different user is to
specify a different ssh key.
the idiomatic way of storing non-default ssh keys is in the location
`~/.ssh/key_name`. "ssh_key_file" can be specified as `key_name`,
for keys in the default location, or as a relative or absolute custom
location eg. `/other_keys/.ssh/nym1` or `../.ssh/nym1`.
BREAKING CHANGE: in nostr git url nym1@ssh/npub123/identifer, nym1 is
now treated as ssh key file location rather than a ssh user. it can
be specified as a file within `~/.ssh` eg `~/.ssh/nym1` or a full or
relative path.