DanConwayDev

> When using ngit as a library and not building in nix - it wasnt available when running tests. maybe out of scope - no biggie! :) > > great...

> please list what PRs you would like to include. I closed the others - I will stack them. I meant if you were making changes to a number of...

I look foward to seeing what you come up with :)

I thought about changing `["clone" "",...]` to multiple `["c" ""]` in the announcement event. This would allow clients to go from a patch or an issues created with the `i`...

@fiatjaf @dluvian @Silberengel @chebizarro @Pleb5

> Isn't this use case covered by the fact that you don't need to be a maintainer, to issue a repo announcement? According to nip34 creating a repo announcement shows...

> Is there a way to associate announcements? You associate the announcements by each listing the other maintainers in the `maintainers` tag. When sending a patch, issue, PR, etc clients...

I can see your adversion to a canonical "t" tags is consistant with your [NIP-51 comment](https://jumble.social/notes/nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqythwumn8ghj7cnfw33k76twv4ezuum0vd5kzmp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uqzpdjk8pqu62fr7qmerq8v2j43vknykspsmf63dsfyt7n8znzdnk58zccgfa) "To me sets with canonical names are an antipattern" but I thought using a...

That is the happy path. But what happens if the repository announcement doesnt list grasp servers, or the grasp servers they list are offline, or dont accept your ref for...

Actually, its a slightly diffeent flow you outlined. 1. You generate a draft PR event with a server hint as a clone tag. 2. push your commit to `refs/nostr/` at...