Remove unneeded implementation detail description.

This commit is contained in:
Gary R Krause 2023-03-04 11:40:07 -05:00
parent 1bb4fa0a47
commit 2a6074eb87

2
69.md
View File

@ -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 ### 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. 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.