Originally introduced in GitLab 11.4 as a GitLab Premium feature, Merge Request Reviews allow merge request reviewers to:
#Second issue board view gitlab code#
That still can help for code review activity.Ħ years later, for GitLab 13.1 (June 2020): Merge Request Reviews moved to Core Your team members can comment on the merge request in general or on specific lines with line comments. (July 2013) There is no possibility yet to comment on each line though, only at the file level.ĭaniel Sokolowski mentions in the comments that Per line comments are now supported (09/2014): Note: since GitLab 6.4, side-by-side diff view is available: see " pull request 5308". It is new!Īm I barking up the wrong tree here? Is there an actual code-review tool I can use in GitLab, or are merge requests the way to go, and if they are am I using them incorrectly? what's the best way to set up a proper code review here? If I issue a merge request for that dev branch from integration I see 10 commits each of which show the incremental changes made to the file. It is a new file but I've submitted changes to it over 10 commits on a dev branch. For example, let's say I have a file I want to review. I seem to only be able to view diffs generated for each individual commit. An issued merge request shows all of the commits between one branch and the other. Some of my searching has indicated that 'Merge Requests' are the way to go.
#Second issue board view gitlab how to#
How does one set up a code review using Gitlab? I see it listed as a feature on the Gitlab website, but I can't seem to find instructions on how to set one up (For that matter, any link to a Gitlab user manual would be most appreciated).
0 kommentar(er)
