GitLab GitLab Group Kickoffs - Create:Source Code, 16 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.4 Kickoff - Create:Source Code

Description

The PM (Daniel Gruesso) from the Create:Source Code group covers the items planned for GitLab release 13.4, shipping on Sept 22, 2020.

A

Hi, my name is daniel cruzo, I'm the product manager for the source code group in the create stage of the devops lifecycle, and today I want to share with you the kickoff for gitlab release 13.4, which will be shipping on the 22nd of september. So, let's get right to it. First thing we're going to work on is going to be adding a dedicated reviewer section to merge requests.

A

So today, assigning a merge request for review is largely done by using the assignee field as a proxy for our viewer, and what we want to do is we want to have a discrete field for reviewers and that will basically have a couple benefits, the largest one being that as a as an approver or reviewer, I will already know who has been giving feedback and there is not going to be duplicate effort of somebody else coming in and giving the same feedback.

A

um But, more importantly, if you are a peer or if you are an author who has not interacted with this merch request in some time, you will immediately know who's responsible to give you feedback on it, and you can reach out to that person directly so largely in the same manner and the same pattern that we use with assignees.

A

You will have a drop down where you can select more or one users here to give you feedback on your commercial quest, so very excited about this one and the second one ties into directly with the first one. uh The second thing is: displaying approval rules that match a given reviewer.

A

So if your merge request- or your project has certain rules where certain groups or certain users have to approve your changes, knowing who those users are it's going to be important and the time of selecting a reviewer, because you want to select a reviewer that is going to be able to fulfill those rules and give you the approvals.

A

You need to merge that code so uh on the drop down alongside the name of the user, we're going to display the information of the approval rule that is linked to that user, and hopefully this will make the process of selecting a user to to review your merge request. Much simpler.

A

The next thing that we're going to work on is going to be an improvement to multi-line merch request comments so right now, as you may know, you are able to comment on multiple lines of the diff and the merge request, and we do this by um clicking on the drop-down and selecting the first line that that coming to start over, so we want to make that easier, and uh the pattern that we want to use here is going to be a click and drag approach where you can click on the first line, where your comment should start and drag to the last line that will make it easier to use and more friendly.

A

The next thing that we're going to work on is going to be updating, auto devops to support code intelligence. So recently we shipped the coding intelligence feature that works natively in gitlab, with no additional um tools needed, and all you need to do is add a job to your gitlab.ci.yaml file.

A

If you're, a user of auto, auto devops um you're going to be able to take advantage of uh code intelligence if you're using the go language, that's where we're starting with since it's the elsif indexer that uh it's kind of ready to go and has been tried and tested.

A

So for all of those projects that are using auto devops and the go language you're going to be able to get that code, intelligence right out of the box. So it's our first step to add support for auto devops as those indexers become more mature and we have more ready support for those languages we'll be adding those to other devops as well, and the last thing that we're going to work on is going to be automatically pruning on referenced.

A

Lfs objects of your repo. So when you are making changes to your files, there may be objects that get left behind that are not referenced by any part of your code or your repo. Right. Now those lfs objects have to be cleaned manually and what we want to do is we want to do that automatically for users so that you are using your resources in space in the most effective manner possible. um So that's largely it for the features that the main features we're going to be working on.

A

We're also going to be working on a bunch of improvements for the performance of merge requests. So some of the things that we're going to work on there should give you a speeder um experience and uh we're gonna make those things more lightweight um and faster to use. So that's it for the release um 13.4 of gitlab. As always, your feedback is welcome. Please reach out and we'll see you on the next one. Bye.