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

MUST have content for the event so clients have something to display.

Browse Source
This commit is contained in:
Gary R Krause 2023-02-14 19:03:02 -05:00
parent f911a99754
commit ac80fdb755
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
69.md
View File

@ -12,7 +12,7 @@ This NIP defines ways source control (git, etc.) context can be stored using nos
`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. `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 MUST contain a text description or summary of the base repository. This enables clients that don't specifically handle this kind to display meaningful text in their UI.
```json ```json
{ {
@ -21,7 +21,7 @@ The `content` of a Source Control Event MAY contain a text description of the ev
"tags": [ "tags": [
["b", <repository url>, <repository url>, ...], ["b", <repository url>, <repository url>, ...],
], ],
"content": <arbitrary string>, "content": <summary or description>,
... ...
``` ```