added as dluvian implemented the title as a `subject` tag in voyage
which caused the issue title not to display in may clients such as:
amethyst, Nostter, nostrudel, coracle and gitworkshop.
nostr:nevent1qvzqqqqx25pzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqy88wumn8ghj7mn0wvhxcmmv9uqzqqta74rkqgzt4akdw3acrparwnq46u2dusg4fzuu2d7ppyhgcmu6kz2ahd
so that the event can be used as a source of truth for the state of refs
such as branches and tags
this could be useful as:
1. a way to reduce trust in git server(s) so they no longer act as a
source of truth. a nip34 git remote-helper could proxy requests to
git servers and only pull updates when they match the state listed in
the repo event.
2. a form of authorisation for nip34 git server implementations
such as song
3. a way of enabling experimentation with other protocols for hosting
and accessing git data. eg a blossom git remote helper
earliest-unique-commit r tag enables clients to:
- retrieve all repo events refering to a local git repo
- group repo events with different identifers that refer to same repo
- retrieve all patches for a local repo,
irespective of the tagged repo event
current-commit-id r tag enables clients to prevent accidental submission of a patch,
which has already been proposed
root-revision tag enables clients to filter out proposal revisions
from a list of proposals
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>
