Commit Graph

12 Commits

Author SHA1 Message Date
Terry Yiu
95885afe2d
Update NIP-09 to rename deletion to retraction 2024-08-14 20:08:41 -04:00
DanConwayDev
788ffb03a0 nip34: add refs to repo event
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
2024-08-01 13:34:19 -03:00
Yasuhiro Matsumoto
3451f5a0c8
fix typos 2024-07-22 22:55:51 +09:00
Adam Shannon
cb9bddb8df all: minor spelling fixes 2024-05-11 11:52:32 -05:00
fiatjaf
bad8826211 nip34: simplify r tag for earliest unique commit. 2024-04-29 14:37:40 -03:00
DanConwayDev
403b5199a4 NIP-34: add status events
merge-commit and applied-commit-id tags enable discussion of patches to be
mapped to lines of code accepted into the master branch
2024-04-17 17:46:34 -03:00
DanConwayDev
0b62729e31 NIP-34: clarify cover letters
remove cover letters from 'possible things to be added later' and
add a clarification that can they can be added through patches
2024-04-17 17:46:34 -03:00
DanConwayDev
8225a018c7 NIP-34: optional tags to improve discoverability
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
2024-04-17 17:46:34 -03:00
DanConwayDev
cb0d35a5f9 NIP-34: optional additional repo maintainers
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
2024-04-17 17:46:34 -03:00
DanConwayDev
46ea8dcf9c NIP-34: add repo-id standard
suggested guidance for repo-id
2024-04-17 17:46:34 -03:00
DanConwayDev
d607a288b5 NIP-34: clarify nip10 thread application
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
2024-04-17 17:46:34 -03:00
fiatjaf_
9a283796ce
NIP-34: git stuff (#997)
* 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>
2024-03-05 08:57:59 -03:00