nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-21 16:15:51 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add subject and t tags to git issues (#1446)

Browse Source 
* 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
This commit is contained in:
dluvian 2024-09-20 14:08:47 -06:00 committed by GitHub
parent ff39a11611
commit ea36ec9ed7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
34.md
View File

@ -104,7 +104,9 @@ The first patch in a series MAY be a cover letter in the format produced by `git
## Issues
Issues 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.
Issues 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.
Issues 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.
```json
{
@ -113,6 +115,9 @@ Issues are Markdown text that is just human-readable conversational threads rela
"tags": [
["a", "30617:<base-repo-owner-pubkey>:<base-repo-id>"],
["p", "<repository-owner>"]
["subject", "<issue-subject>"]
["t", "<issue-label>"]
["t", "<another-issue-label>"]
]
}
```

4
README.md
View File

@ -262,7 +262,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
| `q` | event id (hex) | relay URL | [18](18.md) |
| `r` | a reference (URL, etc) | -- | [24](24.md), [25](25.md) |
| `r` | relay url | marker | [65](65.md) |
| `t` | hashtag | -- | [24](24.md) |
| `t` | hashtag | -- | [24](24.md), [34](34.md) |
| `alt` | summary | -- | [31](31.md) |
| `amount` | millisatoshis, stringified | -- | [57](57.md) |
| `bolt11` | `bolt11` invoice | -- | [57](57.md) |
@ -289,7 +289,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
| `relay` | relay url | -- | [42](42.md), [17](17.md) |
| `relays` | relay list | -- | [57](57.md) |
| `server` | file storage server url | -- | [96](96.md) |
| `subject` | subject | -- | [14](14.md), [17](17.md) |
| `subject` | subject | -- | [14](14.md), [17](17.md), [34](34.md) |
| `summary` | summary | -- | [23](23.md), [52](52.md) |
| `thumb` | badge thumbnail | dimensions in pixels | [58](58.md) |
| `title` | article title | -- | [23](23.md) |