upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
path: root/34.md
diff options
context:
space:
mode:
authordluvian <133484344+dluvian@users.noreply.github.com>2024-09-20 14:08:47 -0600
committerGitHub <noreply@github.com>2024-09-20 17:08:47 -0300
commitea36ec9ed7596e49bf7f217b05954c1fecacad88 (patch)
tree61af5a10693bc8e9a6291aa46eb5a109af158e42 /34.md
parentff39a11611a7f4732550e55d03286c5b1d17467e (diff)
Add `subject` and `t` tags to git issues (#1446)
* Add subject and and l tags to git issues * Replace `l` with `t` tags * Add nip34 to tag table * List nip34 under subject instead of summary
Diffstat (limited to '34.md')
-rw-r--r--34.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/34.md b/34.md
index 9363aeb..35bc1be 100644
--- a/34.md
+++ b/34.md
@@ -104,7 +104,9 @@ The first patch in a series MAY be a cover letter in the format produced by `git
104 104
105## Issues 105## Issues
106 106
107Issues are Markdown text that is just human-readable conversational threads related to the repository: bug reports, feature requests, questions or comments of any kind. Like patches, these SHOULD be sent to the relays specified in that repository's announcement event's `"relays"` tag. 107Issues are Markdown text that is just human-readable conversational threads related to the repository: bug reports, feature requests, questions or comments of any kind. Like patches, these SHOULD be sent to the relays specified in that repository's announcement event's `"relays"` tag.
108
109Issues may have a `subject` tag, which clients can utilize to display a header. Additionally, one or more `t` tags may be included to provide labels for the issue.
108 110
109```json 111```json
110{ 112{
@@ -113,6 +115,9 @@ Issues are Markdown text that is just human-readable conversational threads rela
113 "tags": [ 115 "tags": [
114 ["a", "30617:<base-repo-owner-pubkey>:<base-repo-id>"], 116 ["a", "30617:<base-repo-owner-pubkey>:<base-repo-id>"],
115 ["p", "<repository-owner>"] 117 ["p", "<repository-owner>"]
118 ["subject", "<issue-subject>"]
119 ["t", "<issue-label>"]
120 ["t", "<another-issue-label>"]
116 ] 121 ]
117} 122}
118``` 123```