Replying to Avatar DanConwayDev

Its because the 'earliest unique commit' doesnt match the initial commit. So it can't find it automatically.

Ngit doesn't store the selected repository yet so it tries to find it each time.
39
purple.co 1y ago

Can we add naddr to yaml and use if not empty?

Reply to this note

Please Login to reply.

Discussion

Avatar
DanConwayDev 1y ago

naddr is encoded kind, npub, identifer and optional relays. The missing piece in maintainers.yaml is identifier. we could potentially add that.

39
purple.co 1y ago

how ? specs ? i think is ok for maintainers.yaml to point to right address/identifier ( like git remote ? ) and use/cache/change.

Avatar
DanConwayDev 1y ago

like this:

```

identifier:

gitworkshop

maintainers:

- nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr

relays:

- wss://relay.damus.io

- wss://nos.lol

- wss://relay.nostr.band

```

maintainers.yaml is not in the nip34 spec. If we sort out the clone UX, I think the file is only really useful for a minority of repositories.

39
purple.co 1y ago

how about if is part of rust-nostr-ngit sdk ? Maybe git extension can be put in crate as a extension. If is used every time I try pull or list, is not a "minority".

Avatar
DanConwayDev 1y ago

You are right in that ngit currently looks for the maintainers.yaml every time to identify the maintainers. What I mean is that it doesn't need to. Ideally when a user first uses ngit on a repository (either by cloning the repo using ngit, a feature not yet built, or throug `ngit list`) they should choose a pubkey:identifer to trust.

39
purple.co 1y ago

I think the idea is not to enter naddr every time, and have that store/compute. Is like url for a remote after clone, just a reference that you use, and not have to input after , for any operation.