1 00:00:01,819 --> 00:00:05,000 Meanwhile, we can do a few settings regarding marriage requests. 2 00:00:07,440 --> 00:00:10,530 So if we go to Settings Repository. 3 00:00:13,490 --> 00:00:19,850 There are a few things that we can configure to, for example, if we go to protected branches. 4 00:00:22,240 --> 00:00:29,170 It can change a bit our workflow, so, for example, allow to merge, we should be allowed to merge 5 00:00:29,170 --> 00:00:31,600 as maintainers, developers. 6 00:00:31,840 --> 00:00:33,280 It really depends up to you. 7 00:00:33,820 --> 00:00:37,540 What's actually interesting is allowed to push and we can set it to No. 8 00:00:37,540 --> 00:00:37,810 One. 9 00:00:38,440 --> 00:00:44,050 And what this will actually mean is that nobody is allowed to push changes to master. 10 00:00:44,320 --> 00:00:50,410 So all the changes that will go in the repository must go through the process of creating a much request. 11 00:00:52,800 --> 00:01:00,000 Additionally, if we go to settings general, there are different things we can configure regarding 12 00:01:00,600 --> 00:01:04,200 my request, so I'm going to expand here, my request. 13 00:01:07,230 --> 00:01:15,420 And what I generally like to do is to you as fast forward March, and that will make no much comets 14 00:01:15,420 --> 00:01:16,090 in between. 15 00:01:16,110 --> 00:01:19,200 So the history of digital repository will look very clean. 16 00:01:19,200 --> 00:01:26,880 You will not even know that comet that has come into a repository is actually from a request and from 17 00:01:26,880 --> 00:01:27,750 a separate branch. 18 00:01:29,190 --> 00:01:31,620 So this is, in fact, something very interesting to note. 19 00:01:32,610 --> 00:01:34,260 Additionally, you can. 20 00:01:35,370 --> 00:01:37,500 Check that pipelines might succeed. 21 00:01:39,010 --> 00:01:42,550 And addition, if you're doing code reviews, you can check that as well. 22 00:01:42,760 --> 00:01:47,050 And if there are any discussions on the request, you can easily see that.