diff options
| author | Vitor Pamplona <vitor@vitorpamplona.com> | 2025-03-26 08:38:47 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-26 09:38:47 -0300 |
| commit | 86fc82ce4affe1f10fa5cab787a710105217b26c (patch) | |
| tree | ee79e7a2214f143750803c97b363ea5b77caa14a /34.md | |
| parent | 0619f370bca3485bb9c5870bc2defa03c7c3d10e (diff) | |
Deprecates git replies in favor of NIP-22 (#1744)
Diffstat (limited to '34.md')
| -rw-r--r-- | 34.md | 19 |
1 files changed, 1 insertions, 18 deletions
| @@ -125,24 +125,7 @@ Issues may have a `subject` tag, which clients can utilize to display a header. | |||
| 125 | 125 | ||
| 126 | ## Replies | 126 | ## Replies |
| 127 | 127 | ||
| 128 | Replies are also Markdown text. The difference is that they MUST be issued as replies to either a `kind:1621` _issue_ or a `kind:1617` _patch_ event. The threading of replies and patches should follow NIP-10 rules. | 128 | Replies to either a `kind:1621` _issue_ or a `kind:1617` _patch_ event should follow [NIP-22 comment](22.md). |
| 129 | |||
| 130 | ```jsonc | ||
| 131 | { | ||
| 132 | "kind": 1622, | ||
| 133 | "content": "<markdown text>", | ||
| 134 | "tags": [ | ||
| 135 | ["a", "30617:<base-repo-owner-pubkey>:<base-repo-id>", "<relay-url>"], | ||
| 136 | ["e", "<issue-or-patch-id-hex>", "", "root"], | ||
| 137 | |||
| 138 | // other "e" and "p" tags should be applied here when necessary, following the threading rules of NIP-10 | ||
| 139 | ["p", "<patch-author-pubkey-hex>", "", "mention"], | ||
| 140 | ["e", "<previous-reply-id-hex>", "", "reply"], | ||
| 141 | // rest of tags... | ||
| 142 | ], | ||
| 143 | // other fields... | ||
| 144 | } | ||
| 145 | ``` | ||
| 146 | 129 | ||
| 147 | ## Status | 130 | ## Status |
| 148 | 131 | ||