docs(proto): list the note events of Watch
2 files · +12 -9
M gen/ermite/ermiteconnect/event.connect.go +8 -6
| @@ -47,7 +47,8 @@ type EventServiceClient interface { | |||
| 47 | 47 | // | |
| 48 | 48 | // The events are repo_created, repo_updated, repo_deleted, pushed, gap and, | |
| 49 | 49 | // for merge requests, merge_request_opened, merge_request_merged, | |
| 50 | - | // merge_request_closed and comment_added. Each one is delivered on the | |
| 50 | + | // merge_request_closed, comment_added, comment_edited, comment_deleted and | |
| 51 | + | // comment_resolved (a thread resolved or reopened). Each one is delivered on the | |
| 51 | 52 | // "repo:<name>" topic of its repository and on "home", subject to the | |
| 52 | 53 | // visibility of the repository. | |
| 53 | 54 | // | |
| @@ -60,8 +61,8 @@ type EventServiceClient interface { | |||
| 60 | 61 | // is not guaranteed, between jobs and runs or between two updates of the same | |
| 61 | 62 | // one: a client keeps the copy with the higher Run.version or | |
| 62 | 63 | // RunJob.version and drops the other. There is no event for a change of title or | |
| 63 | - | // description, nor for a resolved comment: after a gap, or to see such | |
| 64 | - | // changes, clients read the merge request again. A merge publishes | |
| 64 | + | // description: after a gap, or to see such changes, clients read the merge | |
| 65 | + | // request again. A merge publishes | |
| 65 | 66 | // merge_request_merged, then pushed for the target branch. | |
| 66 | 67 | // | |
| 67 | 68 | // The server keeps a bounded buffer of recent events. With resume_after set, | |
| @@ -119,7 +120,8 @@ type EventServiceHandler interface { | |||
| 119 | 120 | // | |
| 120 | 121 | // The events are repo_created, repo_updated, repo_deleted, pushed, gap and, | |
| 121 | 122 | // for merge requests, merge_request_opened, merge_request_merged, | |
| 122 | - | // merge_request_closed and comment_added. Each one is delivered on the | |
| 123 | + | // merge_request_closed, comment_added, comment_edited, comment_deleted and | |
| 124 | + | // comment_resolved (a thread resolved or reopened). Each one is delivered on the | |
| 123 | 125 | // "repo:<name>" topic of its repository and on "home", subject to the | |
| 124 | 126 | // visibility of the repository. | |
| 125 | 127 | // | |
| @@ -132,8 +134,8 @@ type EventServiceHandler interface { | |||
| 132 | 134 | // is not guaranteed, between jobs and runs or between two updates of the same | |
| 133 | 135 | // one: a client keeps the copy with the higher Run.version or | |
| 134 | 136 | // RunJob.version and drops the other. There is no event for a change of title or | |
| 135 | - | // description, nor for a resolved comment: after a gap, or to see such | |
| 136 | - | // changes, clients read the merge request again. A merge publishes | |
| 137 | + | // description: after a gap, or to see such changes, clients read the merge | |
| 138 | + | // request again. A merge publishes | |
| 137 | 139 | // merge_request_merged, then pushed for the target branch. | |
| 138 | 140 | // | |
| 139 | 141 | // The server keeps a bounded buffer of recent events. With resume_after set, | |
| @@ -47,7 +47,8 @@ type EventServiceClient interface { | |||||
| 47 | // | 47 | // | ||
| 48 | // The events are repo_created, repo_updated, repo_deleted, pushed, gap and, | 48 | // The events are repo_created, repo_updated, repo_deleted, pushed, gap and, | ||
| 49 | // for merge requests, merge_request_opened, merge_request_merged, | 49 | // for merge requests, merge_request_opened, merge_request_merged, | ||
| 50 | - | // merge_request_closed and comment_added. Each one is delivered on the | 50 | + | // merge_request_closed, comment_added, comment_edited, comment_deleted and |
| 51 | + | // comment_resolved (a thread resolved or reopened). Each one is delivered on the | |||
| 51 | // "repo:<name>" topic of its repository and on "home", subject to the | 52 | // "repo:<name>" topic of its repository and on "home", subject to the | ||
| 52 | // visibility of the repository. | 53 | // visibility of the repository. | ||
| 53 | // | 54 | // | ||
| @@ -60,8 +61,8 @@ type EventServiceClient interface { | |||||
| 60 | // is not guaranteed, between jobs and runs or between two updates of the same | 61 | // is not guaranteed, between jobs and runs or between two updates of the same | ||
| 61 | // one: a client keeps the copy with the higher Run.version or | 62 | // one: a client keeps the copy with the higher Run.version or | ||
| 62 | // RunJob.version and drops the other. There is no event for a change of title or | 63 | // RunJob.version and drops the other. There is no event for a change of title or | ||
| 63 | - | // description, nor for a resolved comment: after a gap, or to see such | 64 | + | // description: after a gap, or to see such changes, clients read the merge |
| 64 | - | // changes, clients read the merge request again. A merge publishes | 65 | + | // request again. A merge publishes |
| 65 | // merge_request_merged, then pushed for the target branch. | 66 | // merge_request_merged, then pushed for the target branch. | ||
| 66 | // | 67 | // | ||
| 67 | // The server keeps a bounded buffer of recent events. With resume_after set, | 68 | // The server keeps a bounded buffer of recent events. With resume_after set, | ||
| @@ -119,7 +120,8 @@ type EventServiceHandler interface { | |||||
| 119 | // | 120 | // | ||
| 120 | // The events are repo_created, repo_updated, repo_deleted, pushed, gap and, | 121 | // The events are repo_created, repo_updated, repo_deleted, pushed, gap and, | ||
| 121 | // for merge requests, merge_request_opened, merge_request_merged, | 122 | // for merge requests, merge_request_opened, merge_request_merged, | ||
| 122 | - | // merge_request_closed and comment_added. Each one is delivered on the | 123 | + | // merge_request_closed, comment_added, comment_edited, comment_deleted and |
| 124 | + | // comment_resolved (a thread resolved or reopened). Each one is delivered on the | |||
| 123 | // "repo:<name>" topic of its repository and on "home", subject to the | 125 | // "repo:<name>" topic of its repository and on "home", subject to the | ||
| 124 | // visibility of the repository. | 126 | // visibility of the repository. | ||
| 125 | // | 127 | // | ||
| @@ -132,8 +134,8 @@ type EventServiceHandler interface { | |||||
| 132 | // is not guaranteed, between jobs and runs or between two updates of the same | 134 | // is not guaranteed, between jobs and runs or between two updates of the same | ||
| 133 | // one: a client keeps the copy with the higher Run.version or | 135 | // one: a client keeps the copy with the higher Run.version or | ||
| 134 | // RunJob.version and drops the other. There is no event for a change of title or | 136 | // RunJob.version and drops the other. There is no event for a change of title or | ||
| 135 | - | // description, nor for a resolved comment: after a gap, or to see such | 137 | + | // description: after a gap, or to see such changes, clients read the merge |
| 136 | - | // changes, clients read the merge request again. A merge publishes | 138 | + | // request again. A merge publishes |
| 137 | // merge_request_merged, then pushed for the target branch. | 139 | // merge_request_merged, then pushed for the target branch. | ||
| 138 | // | 140 | // | ||
| 139 | // The server keeps a bounded buffer of recent events. With resume_after set, | 141 | // The server keeps a bounded buffer of recent events. With resume_after set, | ||
M proto/ermite/event.proto +4 -3
| @@ -17,7 +17,8 @@ service EventService { | |||
| 17 | 17 | // | |
| 18 | 18 | // The events are repo_created, repo_updated, repo_deleted, pushed, gap and, | |
| 19 | 19 | // for merge requests, merge_request_opened, merge_request_merged, | |
| 20 | - | // merge_request_closed and comment_added. Each one is delivered on the | |
| 20 | + | // merge_request_closed, comment_added, comment_edited, comment_deleted and | |
| 21 | + | // comment_resolved (a thread resolved or reopened). Each one is delivered on the | |
| 21 | 22 | // "repo:<name>" topic of its repository and on "home", subject to the | |
| 22 | 23 | // visibility of the repository. | |
| 23 | 24 | // | |
| @@ -30,8 +31,8 @@ service EventService { | |||
| 30 | 31 | // is not guaranteed, between jobs and runs or between two updates of the same | |
| 31 | 32 | // one: a client keeps the copy with the higher Run.version or | |
| 32 | 33 | // RunJob.version and drops the other. There is no event for a change of title or | |
| 33 | - | // description, nor for a resolved comment: after a gap, or to see such | |
| 34 | - | // changes, clients read the merge request again. A merge publishes | |
| 34 | + | // description: after a gap, or to see such changes, clients read the merge | |
| 35 | + | // request again. A merge publishes | |
| 35 | 36 | // merge_request_merged, then pushed for the target branch. | |
| 36 | 37 | // | |
| 37 | 38 | // The server keeps a bounded buffer of recent events. With resume_after set, | |
| @@ -17,7 +17,8 @@ service EventService { | |||||
| 17 | // | 17 | // | ||
| 18 | // The events are repo_created, repo_updated, repo_deleted, pushed, gap and, | 18 | // The events are repo_created, repo_updated, repo_deleted, pushed, gap and, | ||
| 19 | // for merge requests, merge_request_opened, merge_request_merged, | 19 | // for merge requests, merge_request_opened, merge_request_merged, | ||
| 20 | - | // merge_request_closed and comment_added. Each one is delivered on the | 20 | + | // merge_request_closed, comment_added, comment_edited, comment_deleted and |
| 21 | + | // comment_resolved (a thread resolved or reopened). Each one is delivered on the | |||
| 21 | // "repo:<name>" topic of its repository and on "home", subject to the | 22 | // "repo:<name>" topic of its repository and on "home", subject to the | ||
| 22 | // visibility of the repository. | 23 | // visibility of the repository. | ||
| 23 | // | 24 | // | ||
| @@ -30,8 +31,8 @@ service EventService { | |||||
| 30 | // is not guaranteed, between jobs and runs or between two updates of the same | 31 | // is not guaranteed, between jobs and runs or between two updates of the same | ||
| 31 | // one: a client keeps the copy with the higher Run.version or | 32 | // one: a client keeps the copy with the higher Run.version or | ||
| 32 | // RunJob.version and drops the other. There is no event for a change of title or | 33 | // RunJob.version and drops the other. There is no event for a change of title or | ||
| 33 | - | // description, nor for a resolved comment: after a gap, or to see such | 34 | + | // description: after a gap, or to see such changes, clients read the merge |
| 34 | - | // changes, clients read the merge request again. A merge publishes | 35 | + | // request again. A merge publishes |
| 35 | // merge_request_merged, then pushed for the target branch. | 36 | // merge_request_merged, then pushed for the target branch. | ||
| 36 | // | 37 | // | ||
| 37 | // The server keeps a bounded buffer of recent events. With resume_after set, | 38 | // The server keeps a bounded buffer of recent events. With resume_after set, | ||