What about state management of repos, PRs and issues? The author / maintainers should be able to mark them as closed / merged.
Important people of nostr, where you at...
I put a git repo on nostr and I'd like some feedback.
Git repo stored in a kind-0 field, pull requests, issues, etc as regular notes. Thoughts?
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
nostr:npub108kuptq55xrxqc8ttfjqwwhkh7ruur7d3drm2yyp8ul9t86w9g0s3v9usw
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c
Discussion
Any simple template can be used really, that can later be (optionally) automatically processed by specialized client.
Something as simple as putting PULLREQUEST, MERGED, REJECTED etc as the first word of messages in which
the repo is tagged in the usual way.
Simple enough that it doesn't even require specialized software until a repo grows too big.
A couple of dozen issues can be managed manually. Couple of hundred? Use a tool that filters messages...
For example, an open pull request is one that doens't have a reply anywhere down the reply tree, coming from the repo's pubkey starting with the word MERGED or REJECTED,
An open issue is one that doesn't have the reply CLOSED anywhere down the tree coming from the repo account.
Etc... Hand writable, easy to filter w/ software.
Here is an example:
nostr:note1xxt8m3gywkve06lyfgx02mrlusq0qzn4vsrzjp25wnr803n03zfsdql3u6