From the course: Git for Teams
Unlock the full course today
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Code reviews
- [Instructor] So after the code for an issue or feature has been placed into a feature branch and a merge request has been built, the next step in GitFlow is to do a code review of the changes that have been requested to be merged. So we're logged in to GitLab as the maintainer and it's up to the maintainer to review the code, so if they navigate to the Merge Request section they're going to see there's new work for them. They need to look at this merge request and perform a code review. So once you drill down into the merge request, you'll be able to see what changes are found in that request. You can see the commits, so here we see there's one commit within this merge request and to see the files that we need to review, you can click on the Changes tab. So the maintainer takes a look and we say "Well, we kind of wanted feature-a, not just feature." So if we hover over the line that we'd like to comment on, we can click on this Comment button and that allows us to communicate with…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
(Locked)
Teaming with remote platforms overview1m 39s
-
(Locked)
Remote platform selection4m 19s
-
(Locked)
GitLab installation4m 16s
-
GitLab overview4m 36s
-
(Locked)
User account setup4m 44s
-
(Locked)
Account administration and preferences3m 17s
-
(Locked)
Keeping secrets3m 30s
-
(Locked)
Git workflows1m 11s
-
(Locked)
Trunk-based development3m 13s
-
(Locked)
Git flow3m 35s
-
(Locked)
Protecting branches4m 42s
-
(Locked)
Issues6m 59s
-
(Locked)
Feature branches6m 4s
-
(Locked)
Code reviews4m 4s
-
(Locked)
Merging feature branches4m 18s
-
(Locked)
Git Flow wrap-up1m 51s
-
(Locked)
-
-
-