From 2a6074eb8789a376107374086f81c7dcc10e6a48 Mon Sep 17 00:00:00 2001 From: Gary R Krause Date: Sat, 4 Mar 2023 11:40:07 -0500 Subject: [PATCH] Remove unneeded implementation detail description. --- 69.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/69.md b/69.md index 6ab836f..5aeeb2e 100644 --- a/69.md +++ b/69.md @@ -25,8 +25,6 @@ The `content` of a Source Control Event MUST contain a text description or summa ... ``` -A relay MAY host the repository along side it's nostr database which can be discovered using a standard `REQ` message filtering for `kind: 69`. - ### Merge Requests A source control event MAY contain an `m` tag indicating the event is specific to a merge request. If present, the `m` tag SHALL define the branch being merged into and the branch being merged in. An event MAY include the URL of the repository being merged from. This could be included when the URL being merged from is not in the `b` tag of the event or for specificity. When creating a merge request, the `content` field MAY contain a justification/explanation for the merge. The `l` tag MAY be included with an `m` tag. The `l` tag specifies the relative file path and line number that the event is referencing.