合并请求，审阅过程以及在GitLab中使用注释 [英] Merge Request, Review process and using comments in GitLab

问题描述

我们目前正在评估在项目中使用GitLab的情况，而我们发现与审核合并请求时的注释略有不同.

当代码审查中输入了一些注释并推送了新的提交以解决这些注释时，问题就开始了.

在讨论"选项卡上都显示了对提交所做的注释和在更改"面板上所做的注释，但是没有迹象表明对同一行进行了一些更改.转到更改"面板，查看最新的与基准的比较-我完全可以得到期望的结果(到目前为止，分支上的所有工作都已完成)，但是我们没有看到上面覆盖着注释的内容.旧提交或旧评论.

我是在一半的期望中，在讨论面板中，我将在每个注释下得到另一个部分，以显示最近在代码中所做的更改.这样，或者在查看最新的内容时，甚至可以访问在更改"面板中所做的所有评论，甚至包括对较旧版本的评论.

关于GitLab审核过程和管理评论，我这里缺少什么吗?

解决方案

GitLab自2016年以来已经有了长足的发展，并且

甚至更好-您已解决的评论图钉将从设计中消失，因此您可以专注于剩下的内容！

当然，如果需要重新访问某些内容，所有已解决的线程将在侧边栏底部的已解决的注释"区域中可用.从那里，您可以再次找到它们，并查看哪个修订版本适用于该修订版本.

我们认为这将大大改善您的工作流程，因此您可以专注于重要的事情.

请参见

为弥合这些差距，GitLab 13.5引入了合并请求审阅者".这使作者可以轻松地请求评论以及查看评论的状态.
通过简单地从审阅者"中选择一个或多个用户，可以实现以下目的:字段，则分配的审阅者将收到有关审阅合并请求的请求的通知.

这很容易确定合并请求中涉及的用户的相关角色，以及正式请求对等方的审核.

请参见文档和

I was half-expecting that in the discussion panel I'd be getting another section under each comment showing what was changed in the code recently. That, or be able to access all the comments ever made in the "Changes" panel when looking at the latest, even comments made on older versions.

Is there something I'm missing here when it comes to GitLab review process and managing comments?

解决方案

GitLab has evolved considerably since 2016, and the new 13.1 (June 2020) adds a feature which is relevant for your use case:

Mark any Design thread as resolved

When you receive lots of feedback on a Design, the number of comment pins can build up quickly!
As your discussion thread grows, it gets hard to know which discussions are complete and which still need work.

With 13.1, you’ll have the ability to mark any comment as Resolved to signify that it is now complete.

Even better — your resolved comment pins will disappear from the Design so you can focus on what’s left!

And, of course, if you need to revisit something, all of your resolved threads will be available in the Resolved Comment area at the bottom of the sidebar. From there, you can find them again and see which revision applied at the point of revision.

We think this will greatly improve your workflow so you can focus on what is important.

See Documentation and Issue

---

GitLab 13.5 (Oct. 2020) will add a clear distinction between merge-request participants ("assignee") and reviewers:

To bridge these gaps, GitLab 13.5 introduces merge request "reviewers," which easily allows authors to request a review as well as see the status of the review.
By simply selecting one or more users from the "reviewers" field, the assigned reviewers will receive a notification of the request to review the merge request.

This makes it easy to determine the relevant roles for the users involved in the merge request, as well as formally requesting a review form a peer.

Requesting a pull request review is already available for GitHub

---

With GitLab 13.7 (December 2020), you have a clearer definition of reviewers:

Reviewers for Merge Requests

Asking a colleague to review your code should be a routine part of contributing code, but it’s often needlessly complex.

A simple task like asking for a review can lead to confusion. For example, how should you ask? An email? Comment? Chat message?

Without a formal process, reviews can be inconsistent and hard to keep track of. Previously, an option was to assign a reviewer to a merge request, but even with this formality, both the author and the reviewer appeared in the same assignee field, making it hard for other team members to know who was doing what.

GitLab 13.7 introduces reviewers for merge requests, which allows authors to request a review from someone.
The new "Reviewers" field allows users to be designated as reviewers in a similar way to assignees. The reviewers receive a notification inviting them to review the merge request.

This provides a formal process for requesting a review and clarifies the roles of each user in a merge request.

Future iterations will include showing the most relevant reviewers for a merge request as well as a streamlined merge request approval flow that puts reviewers at the center.
You can follow along in the merge request reviewer assignment epic for more details.

See Documentation and Issue.

这篇关于合并请求，审阅过程以及在GitLab中使用注释的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！