... | ... | @@ -41,12 +41,10 @@ Several review-related labels have been added to Gitlab merge requests: |
|
|
|
|
|
A merge request has an "Assignee" field and a "Reviewer" field. If you are assigned to one of those it will show up in "Your Merge Requests".
|
|
|
|
|
|
If the "Reviewer" field is set the next action item is for that person, otherwise the next action item is for the assignee.
|
|
|
|
|
|
When you create a merge request, set the "Assignee" to yourself. Typically you are the one that is responsible for merging it eventually. You can change the "Assignee" if someone is taking over the work, but in most cases the one who created the merge request will stay the assignee.
|
|
|
|
|
|
The "Reviewer" label is initially left Unassigned. A merge request with the "Review" label set and no assigned reviewer is awaiting review.
|
|
|
When the merge request is ready for review, add the "Review" label and set the "Assignee" field to unassigned. Merge requests with those attributes are ready for review.
|
|
|
|
|
|
If you start reviewing a merge request, assign yourself. You are now the reviewer. When you are done with the review, you can unassign yourself. This means the action item is back to the "Assignee".
|
|
|
The "Reviewer" label is left Unassigned. The sole purpose of this field is to request a review from a specific person. As author (or on behalf of the author) of the merge request you can set it to indicate so.
|
|
|
|
|
|
The assignee can also set the "Reviewer" field to indicate it requests code review from a specific person. |
|
|
\ No newline at end of file |
|
|
If you start reviewing a merge request, set the "Assignee" field to yourself. You are now the reviewer. When you are done with the review, you should assign the merge request back to the author, indicating the action item is back to the author. |
|
|
\ No newline at end of file |