npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror, branch v1.2.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/atom?h=v1.2.02024-05-14T05:30:45+00:00chore: bump to v1.2.02024-05-14T05:30:45+00:00DanConwayDevDanConwayDev@protonmail.com2024-05-14T05:30:45+00:00urn:sha1:f5c82ee70dc2e881c2b1013f6d352f5da7b08291
changelog:
* remove unreliable relay.f7z.io from default relay set
* `ngit send --in-reply-to` tag any nostr notes and npubs in proposals
* `ngit send` link to proposal on gitworkshop
feat(send): `in-reply-to` tags npubs and events2024-05-07T08:10:33+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-22T06:26:15+00:00urn:sha1:10498b953d36304b441fcb162155c2487046206f
in addition to being used to create a new proposal revision,
in-reply-to can now be used to reference other events and npubs.
for example an issues or kind 1 threads where the proposal is relevant
the proposal will only be marked as a revision if the first parameter is
a reference to an existing proposal root
fix: remove relay.f7z.io from default relays2024-04-24T06:34:14+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-24T06:34:14+00:00urn:sha1:c4853f69dc25408ff70cccbe923d2cd400385fc2
as over the last 2-3 weeks it has consitantly be timing out
feat(send): print link to proposal root2024-04-22T08:29:18+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-22T08:29:18+00:00urn:sha1:6bfd8b0ddec7f8f4c24a97d357de9acd615b0b17
after a new root proposal has been sent
link directly to gitworkshop.dev as well as njump.me until
gitworkshop is added to njump
build: fix lint warning2024-04-19T15:13:21+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-19T15:13:21+00:00urn:sha1:4b49ab05e3b8fa3146d7dfd0c8e5250c14df46ae
remove unused binding
chore: bump to v1.1.22024-04-16T15:32:19+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-16T15:32:19+00:00urn:sha1:87ee59ebd91ec4b73b5528446e6d7d87449a9e5d
changelog:
* improve relay timeout behaviour
* fix `ngit init` handling of multiple values eg `clone`
* improve reliability via with dependancy upgrade
* build via nix in ci
build: update cargo.toml homepage and repo2024-04-16T15:28:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-16T15:28:00+00:00urn:sha1:89d9527d5f00b246fa2b689a6af1e8d5206307ce
away for github and towards gitworkshop.dev
chore: cargo update2024-04-15T14:28:33+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-15T14:28:33+00:00urn:sha1:6cd07ec0ac56450e2d4853854b1338ae445bd76c
update dependancies to latest version stated in cargo.toml
feat: reduce connection timeout 6s ~> 3s2024-04-10T10:41:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-10T10:41:00+00:00urn:sha1:ba83cc575ec97c313841c79e2a1afd448d8b9fe5
seperate connection timeout from get_events_of timeout and reduce it to 3s
chore: update rust nightly in nix2024-04-09T08:45:57+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-09T08:45:57+00:00urn:sha1:7415be21c725e4d1758cff4924783dd4623c2554
whilst fmt is using nightly it doesnt appear that clippy is
previous attempts to update the rustfmt nightly version have resulted
in a large number of errors which needed resolving. the change was
backed out because of other priorities.
It appears now that clippy is not using the nightly version
and there are no regressions