npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/sub_commands, branch v1.7.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.7.12024-09-04T12:30:59+00:00refactor: organise into lib and bin structure2024-09-04T12:30:59+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-04T07:04:48+00:00urn:sha1:949c6459aa7683453a7160423b689ceadb08954b
the make the code more readable
this commit just moves the files, the next commit should fix the imports
feat(init): https as default clone url protocol2024-09-03T14:22:56+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-03T10:01:14+00:00urn:sha1:a0fdc17426afa0e55a2a3b733983bab763226e5a
so clone urls align to fetch rather than push.
see discussion here:
nostr:nevent1qvzqqqqx25pzpp59a0hkv5ecm45nrckvmu7pnk0sukssvly33u3wwzquy4v037hcqyxhwumn8ghj7mn0wvhxcmmvqqs2tdha5ymadffrkdprachsz6gsgsy6kc8gkntgq750mfn7u3aeu3g7xt8k9
chore: bump rust-nostr to v0.34.02024-08-28T15:42:53+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-28T13:20:34+00:00urn:sha1:a5216602749bff55c2773acce098c91942cd3920
bump all rust-nostr packages
I'm not sure I'm completely happy with allowing mutable_key_type
but it is just run inside tests
it appears that Event didn't have the Copy trait in v0.33.0 so I'm
not sure why this warning suddenly appeared
the timeout of client.get_events_of needed to be doubled which could
indicate that an ineffiency has been introduced in v0.34.0
the primary motivation for upgrading now was to get this fix:
nostr:nevent1qqsffl2ld678pjj77rh9k2g4edljmxdu6ew4lvgnglxv7jhu3ru8vvcpp4mhxue69uhkummn9ekx7mqzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6rm2ucm
as I suspect it is also effecting other repositories
eg nostr-profile-manager
fix(init): make maintainer.yaml copy clearer2024-08-27T13:06:46+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-27T13:06:46+00:00urn:sha1:eaeea28999b457d3a0038142e33ff3cd487f8fa7
as this has reduced in importance as the user begins by
selecting a trusted maintainer
feat: set proposal branch prefix to `pr/`2024-08-20T05:25:17+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-20T05:25:17+00:00urn:sha1:fedf5166f0c57db14b9e43747121e4b7845b63dd
from `prs/`.
whilst plural reflects usage of `heads` and `tags` in git refs,
singular is shorter and more reflective of usage of branch prefixes
such as `feature/` `fix/`
feat(remote): `push` new proposal2024-08-09T07:40:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-09T07:35:53+00:00urn:sha1:5618fd9883d45de1443a40abada944cbe3bb8dfd
issue new proposal when new branch is pushed into `prs/*` namespace,
which doesn't match an existing proposal
fix(send): patch count2024-08-08T16:53:42+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-08T16:53:42+00:00urn:sha1:a556464452789dc72cb9b0bff8e9ba6addc6639a
fix [PATCH n/n] when no cover letter and patches great than 1
fixes error where the first patch would be
[PATCH] followed by [PATCH n/n]
Revert "refactor: fix `stderr` ~> `stdout`"2024-08-01T16:18:53+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-01T16:18:53+00:00urn:sha1:2de11e4099a1f841666eac6a1f68389b01c3398b
This reverts commit 3d2e031294b467be725a4ac5f5e65e029d25699a.
refactor: fix `stderr` ~> `stdout`2024-08-01T14:49:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-01T14:49:47+00:00urn:sha1:3d2e031294b467be725a4ac5f5e65e029d25699a
as `stderr` is being used when it shouldn't be
feat(remote): `push` issues state event2024-07-31T14:59:17+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-31T14:59:17+00:00urn:sha1:3acdeabfc3ab55d3e92d76d92d8ab6ad0383dd09
if no previous state events can be found it replicates git server
otherwise it just updates pushed value