nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 08:55:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update NIP numbering

Browse Source
This commit is contained in:
Gary R Krause 2023-02-14 18:58:55 -05:00
parent 603f1911a9
commit f911a99754
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
draft.md → 69.md
View File

@ -1,4 +1,4 @@
NIP-?? NIP-69
====== ======
Source Control Context Source Control Context
@ -6,18 +6,18 @@ Source Control Context
`draft` `optional` `author:garyKrause_` `draft` `optional` `author:garyKrause_`
This NIP defines ways source control (git, etc.) context can be stored using nostr. Git is already decentralized, but the contexts around a git repository are largely centralized (PR comments, issue tracking, releases, etc). With the correct approach a nostr relay could store this context using many of the existing NIPs. This NIP defines a new kind, `kind: ??`, to represent a source control repository. This NIP purposely does not indicate git as a requirement but many of the concepts will be based around git methods of source control. The author hopes that the NIP is flexible enough to accommodate other source control methodologies. This NIP defines ways source control (git, etc.) context can be stored using nostr. Git is already decentralized, but the contexts around a git repository are largely centralized (PR comments, issue tracking, releases, etc). With the correct approach a nostr relay could store this context using many of the existing NIPs. This NIP defines a new kind, `kind: 69`, to represent a source control repository. This NIP purposely does not indicate git as a requirement but many of the concepts will be based around git methods of source control. The author hopes that the NIP is flexible enough to accommodate other source control methodologies.
## Definition of a Source Control Event ## Definition of a Source Control Event
`kind: ??` uses tag the `b` tag to identify the base repository. The value of this tag SHALL be a list of remote source control repository URLs. These URLs MAY be a nostr relay URL or a traditional repository URL. The first URL in this list SHALL be considered the "default" repository URL for the context. `kind: 69` uses tag the `b` tag to identify the base repository. The value of this tag SHALL be a list of remote source control repository URLs. These URLs MAY be a nostr relay URL or a traditional repository URL. The first URL in this list SHALL be considered the "default" repository URL for the context.
The `content` of a Source Control Event MAY contain a text description of the event or other information about the repository. The `content` of a Source Control Event MAY contain a text description of the event or other information about the repository.
```json ```json
{ {
... ...
"kind": ??, "kind": 69,
"tags": [ "tags": [
["b", <repository url>, <repository url>, ...], ["b", <repository url>, <repository url>, ...],
], ],
@ -25,7 +25,7 @@ The `content` of a Source Control Event MAY contain a text description of the ev
... ...
``` ```
A relay MAY host the repository along side it's nostr database which can be discovered using a standard `REQ` message filtering for `kind: ??`. A relay MAY host the repository along side it's nostr database which can be discovered using a standard `REQ` message filtering for `kind: 69`.
### Merge Requests ### Merge Requests
@ -34,7 +34,7 @@ A source control event MAY contain an `m` tag indicating the event is specific t
```json ```json
{ {
... ...
"kind": ??, "kind": 69,
"tags": [ "tags": [
["b", <repository url>, <repository url>, ...], ["b", <repository url>, <repository url>, ...],
["m": <branch to be merged into>, <branch to be merged in>, <URL of merging in repository>], ["m": <branch to be merged into>, <branch to be merged in>, <URL of merging in repository>],