can be used by clients to tag multiple maintainers in patches
helps clients identify whether multiple repo events for the same repository
are complementary or in competion
for consistancy and so that the intended order of patches is easier to ascertain
enables additional patches to be appended to a patch set, supporting a PR-like workflow alongside
patch-over-email-like workflow
* NIP-34: git stuff.
* repository head.
* threads/issues and replies.
* add "p" optional tags to events.
* add list of things to do later in the end.
* multiple values in some tags instead of multiple tags.
* replace "patches", "issues" tags and replace that with "relays".
* bring in tags that allow for a commit id to be stable.
* edit "reply" kind to say it should follow normal NIP-10 threading rules.
* update "things to be added later".
* add commit time to "committer" tag.
* remove "head" tag.
* mention the possibility of mentioning others users in patches.
Co-authored-by: DanConwayDev <114834599+DanConwayDev@users.noreply.github.com>
* clarify commit-pgp-sig.
* clarify requirements and threading of replies.
* add t=root tag.
---------
Co-authored-by: DanConwayDev <114834599+DanConwayDev@users.noreply.github.com>
