npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/34.md, branch deleting-replaceable[no description]https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/atom?h=deleting-replaceable2024-05-11T16:52:32+00:00all: minor spelling fixes2024-05-11T16:52:32+00:00Adam Shannonadamkshannon@gmail.com2024-05-11T16:52:32+00:00urn:sha1:cb9bddb8dfd11972286215d9bdee7434764ccf7bnip34: simplify `r` tag for earliest unique commit.2024-04-29T17:37:40+00:00fiatjaffiatjaf@gmail.com2024-04-24T21:44:36+00:00urn:sha1:bad8826211ca2eb8660e4bd68b292d14616d3669NIP-34: add status events2024-04-17T20:46:34+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-07T10:21:06+00:00urn:sha1:403b5199a490b6a148063003e00924f5e79ba36c
merge-commit and applied-commit-id tags enable discussion of patches to be
mapped to lines of code accepted into the master branch
NIP-34: clarify cover letters2024-04-17T20:46:34+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-07T09:20:25+00:00urn:sha1:0b62729e318497922822c39471ab31a869563ba5
remove cover letters from 'possible things to be added later' and
add a clarification that can they can be added through patches
NIP-34: optional tags to improve discoverability2024-04-17T20:46:34+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-07T09:01:19+00:00urn:sha1:8225a018c72c4d11b575ed4e57fa587d08c09027
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
NIP-34: optional additional repo maintainers2024-04-17T20:46:34+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-07T08:25:49+00:00urn:sha1:cb0d35a5f9f1b88a270f7fbbfbdb97e095e28d56
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
NIP-34: add repo-id standard2024-04-17T20:46:34+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-07T08:03:48+00:00urn:sha1:46ea8dcf9cedd1f64e9444b70ac0ed24e40bbe1a
suggested guidance for repo-id
NIP-34: clarify nip10 thread application2024-04-17T20:46:34+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-07T07:59:16+00:00urn:sha1:d607a288b5db72a84f3d6cc8fd42304d31e1f66b
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 (#997)2024-03-05T11:57:59+00:00fiatjaf_fiatjaf@gmail.com2024-03-05T11:57:59+00:00urn:sha1:9a283796ce95261c960d1b9ffc13e8f278079956
* 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>