Skip to content

NIP-34: send patches and issues to repos not yet on Nostr #2050

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

NIP-34: send patches and issues to repos not yet on Nostr #2050

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions 34.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,13 +19,16 @@ Git repositories are hosted in Git-enabled servers, but their existence can be a
"tags": [
["d", "<repo-id>"], // usually kebab-case short name
["name", "<human-readable project name>"],
["description", "brief human-readable project description>"],
["web", "<url for browsing>", ...], // a webpage url, if the git server being used provides such a thing
["clone", "<url for git-cloning>", ...], // a url to be given to `git clone` so anyone can clone it
["relays", "<relay-url>", ...], // relays that this repository will monitor for patches and issues

// optional
["description", "brief human-readable project description>"],
["web", "<url for browsing>", ...], // a webpage url, if the git server being used provides such a thing
["r", "<earliest-unique-commit-id>", "euc"],
["maintainers", "<other-recognized-maintainer>", ...],
["t", "<arbitrary string>"], // hashtags labelling the repository
["retired-clone", "<url for git-cloning>", ...] // to continue the association with patches and issues sent to this repository via the `i` tag before this repo maintainer's moved it to nostr
]
}
```
Expand Down Expand Up @@ -80,6 +83,8 @@ The first patch revision in a patch revision SHOULD include a [NIP-10](10.md) `e
"content": "<patch>", // contents of <git format-patch>
"tags": [
["a", "30617:<base-repo-owner-pubkey>:<base-repo-id>"],
// alternatively, if repository state announcement doesnt exist yet use:
["i", "https://github.com/bitoin/bitcoin.git"], // repository git clone url SHOULD use https formation with .git suffix but no trailing slash
["r", "<earliest-unique-commit-id-of-repo>"] // so clients can subscribe to all patches sent to a local git repo
["p", "<repository-owner>"],
["p", "<other-user>"], // optionally send the patch to another user to bring it to their attention
Expand Down Expand Up @@ -115,6 +120,8 @@ Issues may have a `subject` tag, which clients can utilize to display a header.
"content": "<markdown text>",
"tags": [
["a", "30617:<base-repo-owner-pubkey>:<base-repo-id>"],
// alternatively, if repository isn't yey on nostr:
["i", "https://github.com/bitoin/bitcoin.git"], // repository git clone url SHOULD use https formation with .git suffix but no trailing slash
["p", "<repository-owner>"]
["subject", "<issue-subject>"]
["t", "<issue-label>"]
Expand Down