Gitlab hero border pattern left svg Gitlab hero border pattern right svg
GitLab
vs
Crucible
Decision Kit
Decision Kit

Crucible is a web based collaborative code review application.

Feature Comparison
FEATURES

必需的合并请求批准

当项目需要多次验收时,您可以要求每个合并请求在合并之前都得到批准。通过“必需的合并请求批准”,您可以设置必要的批准次数,并预定义特定的审批人清单,从而通过依次审批的方式来保证代码的质量和标准。

Learn more about merge request approvals

多审批人代码审核

极狐GitLab 为确保严格的代码审查,在合并请求能够被合并之前,您可以要求得到批准的最小用户数量。在代码最终合并前,您也可以撤销批准。

Approvals Documentation

代码评审的批准规则

通过指定正确的审批人列表、最小审批者数量以及受保护的目标分支,确保合适的人员使用批准规则来评审合并请求,进而方便的从工程、体验和产品等不同团队请求评审。

Approvals Documentation

Optional Merge Request Approvals

Code review is an essential practice of every successful project, and giving your approval once a merge request is in good shape is an important part of the review process, as it clearly communicates the ability to merge the change.

Learn more about optional merge request approvals

代码所有者

通过将代码所有者分配到CODEOWNERS文件中,以指明负责项目中代码的团队成员。代码所有者能被自动分配为合并请求审批人,可以根据需要进行设置,并在查看文件时显示。

Learn more about Code Owners

代码所有者分段

代码所有者分段支持每个团队独立配置他们自己的代码所有者配置,来让多个团队照看代码库的公共部分。

Learn more about Code Owners Sections

Multi-line diff comments

Leave merge request comments spanning multiple lines in a diff

Image Discussions

Within a commit view or a merge request diff view, and with respect to a specific location of an image, you can have a resolvable discussion. Have multiple discussions specifying different areas of an image.

Image Discussions

Merge Request Commit Discussions

Comment on a commit within the context of a merge request itself

Merge Request Commit Discussions

Inline commenting and discussion resolution

Code or text review is faster and more effective with inline comments in merge requests. Leave comments and resolve discussions on specific lines of code. In GitLab, Merge Request inline comments are interpreted as a discussion and can be left on any line, changed or unchanged. You can configure your project to only accept merge requests when all discussions are resolved.

Learn more about resolving discussions

Code review dashboards

Dashboards with a filterable set of code reviews (could be by project, by user, by branch, by status, or a combination of those). Dashboards includes code review status and links to get to them. This makes it easy to see what is going on with code reviews for a desired subset.

Code review with GitLab

Contributor agreements

Users can be required to sign one or more contributor agreements before being able to submit a change in a project.

Read more on the issue

Robot comments

Support for inline comments that are generated by automated third-party systems, for example robot comments can be used to represent the results of code analyzers.

GitLab merge requests store results

Works with multiple repository types

Supports more than one repository type, such as Git, Subversion, Perforce, CVS, Mercurial.

Learn about migrating from other SCMs