npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src, branch v1.4.6Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.4.62024-09-13T16:23:09+00:00fix(ngit): pull and push find pr from branch2024-09-13T16:23:09+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-13T16:09:10+00:00urn:sha1:61b130e61e3ba88d61f75dd2f6a201e700e7dc01
as since cl.get_branch_name has been introduced branch names
could be prefixed with a pr and sometimes postfixed with an event id
with the fix your branch could be called `article-editor`
or `pr/article-editor`
if you are logged in as the author of the PR (git config nostr.npub
matches the PR author)
or `article-editor(3fbba0ec)` which is what it would be named if you
weren't logged in as the author and checked out the branch on a
remote with the nostr url.
feat(remote): fallback to ssh or https2024-08-30T12:39:05+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-30T12:39:05+00:00urn:sha1:8a9fc6336ae52ed73160719feeae96db9889feb0
ssh clone urls are problematic as it requires authentication for
fetching if users don't ave ssh keys setup for authentication with
the git server. so cloning / fetching will fail.
some users only authenticate using https and some only using ssh
so we cant just use https for everything.
this commit falls back to the other protocol if the first one failed
for list, fetch or push
fix(remote): push pr shoudln't connect to server2024-08-30T09:23:28+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-30T09:23:28+00:00urn:sha1:b4459e98d816f6f278a4e9ab76883008d0b946fe
as reported by arjen and tracked via:
nostr:nevent1qvzqqqqx25pzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqy2hwumn8ghj7ur4wfcxcetjv4kxz7fwvdhk6qpqur335cpnlktwkhv43d8sdk24dpu79jnfuk9qyvk7kga6aencm77sj7e8fa
as our tests are connecting to clone url in the file system its difficult to write a test for this
fix(remote): add auth for ssh `list` and `fetch`2024-08-30T09:09:46+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-30T09:05:41+00:00urn:sha1:f735aeb69942546b4d6c2ae1156d20db2edb24f3
as authentication is always required if clone url is ssh
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
fix(remote): clone failure2024-08-27T10:56:36+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-27T10:56:36+00:00urn:sha1:ec6a6fcc1321c6824e000dda4860cf21e0cdae57
clone fails due to error:
`Error: failed to fetch objects in nostr state event from:`
interestingly this error doesnt appear when the git url is a
local repository in a file server so the tests dont fail
fix:(remote): only maintainers can push2024-08-20T11:32:26+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-20T11:32:26+00:00urn:sha1:09bf648d4a36bc9ada0cff9438aa3b3f98631600
and update / issue a state event.
normal users can only push branches prefiex with pr/
and these go on nostr, not the git server.
fix(remote): `push` tags use correct oid2024-08-20T10:58:17+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-20T10:58:17+00:00urn:sha1:a9a81ed040990a8431c4b4b05bf5deb551732b09
use ^{} postfix for the commit id and without postfix for the tag id
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/`