How to set up code checking with Gitlab?

Question

How to customize code view with gitlab? I see that it is listed as a function on the Gitlab website, but I cannot find instructions on how to install it. (In this regard, any link to the Gitlab user guide would be most appreciated).

Some of my searches have indicated that Merge Requests is the way to go ... but I find them limiting. The merge request issued shows all commits between one branch and another. It seems that I can only see the differences generated for each individual commit. For example, let's say I have a file that I want to view. This is a new file, but I made changes to its 10 commits to dev branches. If I issue a merge request for this dev branch from integration, I see that there are 10 commits, each of which shows the incremental changes made to the file ... I want to look at all this. This is new!

Am I barking the wrong tree here? Is there a real code checking tool that I can use in GitLab, or merge requests is the way to go, and if I use them incorrectly? what's the best way to set up a correct code review here?

Answer 1

Note: since GitLab 6.4, side-by-side diff view is available: see " 5308 Tensile Request ".

(July 2013) There is no way to comment on each line, but only at the file level. Daniel Sokolowski mentions in comments that direct comments are currently supported (09/2014):

Your team members can comment on the merge request as a whole or in specific lines with line comments.

This can still help for code verification.

Answer 2

I have been doing code reviews in Gitlab for over two months, with virtually no friction. I setup rss2email to send email notifications every time a developer pushes new commits. Then I use the Gitlab comment function for commits to make some comments on the pressed code.

Unfortunately, Gitlab does not allow comments on the files themselves, only in commits (such as Github). Whenever I am in a situation where I need to comment on what I missed in the previous commit, I use the guilt tool to find the commit that introduced / changed the section of the code to be commented on.

This is far from perfect, but so far it works well.

Answer 3

You can view the submitted code in Merge Request for another repository or in the current repository.
example http://demo.gitlab.com/diaspora/diaspora/commits/master

Then you can add comments to committed changes to the file ( Reply button) or to everything commit

example http://demo.gitlab.com/diaspora/diaspora/commit/42f47626890218a180870bc3f44ec57625b0779c

As a result, communication is a code review . However, I personally recommend that you review the code on one PC with full-time communication when possible, and use tools to record results or when more formality is required.

For a file revue that has many commits, for example. http://demo.gitlab.com/diaspora/diaspora/blame/master/README.md look at it using blame to see who did what. However, in this view, there is no way to communicate and add comments. I would recommend just adding changes as comments in this case.

Answer 4

Yes. Merge requests are how peer reviews are carried out.

There should be a "diff" tab in which the changes of all commits (mentioned here: http://youtu.be/DyAX8ws5OIc?t=3m2s ) will be displayed.

The video also perfectly explains how it can be used for an expert review.