WEBVTT 00:00.240 --> 00:01.280 Hi guys My name is Scott. 00:01.290 --> 00:06.990 Take an I am from is it I mentioned dot com and welcome to another section of our continuous integration 00:07.080 --> 00:10.740 development and delivery with Azure doe ops course. 00:10.750 --> 00:15.450 And in this section we are going be talking about as you repost and this video we are going to be talking 00:15.450 --> 00:21.450 about an introduction to Azure repos as your reporter said our version control tool that you can use 00:21.450 --> 00:26.820 to manage your code whether you're a software project is a large or small project using version control. 00:26.820 --> 00:29.430 As soon as possible it's a good idea. 00:29.450 --> 00:35.220 And again as your reports provide support for two types of version control systems in Azure which is 00:35.430 --> 00:42.110 good and TAF we see so they get is something that we know it can be a good enterprise or good that they 00:42.110 --> 00:43.980 are using the organization. 00:44.030 --> 00:48.750 It is exactly the same get flavor which is something that you have pretty much used to. 00:48.960 --> 00:54.720 And again you get to something which recently Microsoft acquired so you can see all the different integration 00:54.720 --> 00:56.910 coming in for the favor of gain. 00:57.030 --> 00:58.680 Is also really really awesome. 00:58.710 --> 01:05.250 Within a year though ups servers and the next page which is supported is t of visa our team foundation 01:05.250 --> 01:06.370 version control. 01:06.390 --> 01:11.820 So if I remember the team foundation version control is very very classical and it's been used across 01:11.820 --> 01:17.190 the companies even Microsoft team are actually using team foundation version control system for their 01:17.190 --> 01:22.430 own internal products and it is something that you can only use for the private project. 01:22.440 --> 01:27.840 So the product that we have created in this course is a public project so we cannot actually use the 01:27.890 --> 01:28.730 TFC. 01:28.980 --> 01:31.890 So if we use that we are going to be encountering some error or something like that. 01:32.280 --> 01:39.390 So rather we are going to be getting into the get off the version control systems for this whole course. 01:39.480 --> 01:44.370 And also when you import the card you can also see that our different kinds of sources it is going to 01:44.370 --> 01:50.850 ask something like as your rep will get or get get enterprise server some version bid bucket or other 01:50.850 --> 01:52.940 get that you are pretty much familiar with. 01:52.980 --> 01:56.660 So you can keep on using any one of the source when importing the core. 01:56.860 --> 02:01.400 You are going to perform at release pipeline and again don't worry about these things yet we are going 02:01.400 --> 02:03.900 to be talking about that in our next section. 02:03.900 --> 02:09.100 But in this section we are gonna be dealing something about as your reports are not so with Azure repos 02:09.390 --> 02:16.380 we can do exact same things that we expect to happen with a get RDF easy on code such as creating a 02:16.380 --> 02:21.840 pull request linking the work item to the pull requests setting up a branch policy squash merge pull 02:21.840 --> 02:28.630 request get branch pull requests workflow leaving commons and vote on changes so leaving Commons and 02:28.630 --> 02:33.750 the vote on changes or something pretty new to the game itself and you can keep on adding some smileys 02:33.750 --> 02:38.640 and all those tough features introduced NTFS which was introduced in the bird conference earlier this 02:38.640 --> 02:44.190 year and this is really awesome to see that all these fancy little things are something which community 02:44.190 --> 02:46.670 was expecting to happen for a pretty long time now. 02:47.810 --> 02:53.750 And linking the comments with the task we can also do that as well as you can see there are some tasks 02:53.750 --> 03:00.880 that we could no previous videos and you can see that we can also add the link for the task. 03:00.950 --> 03:07.160 So for instance if I have a link for the source card for the particular brands that we are working for 03:07.160 --> 03:14.060 the speaker of sprint you can link that and once the code has been completed by the developer and once 03:14.060 --> 03:19.730 he is checking in and once it has been approved you can also see the status of the approved being happened 03:19.880 --> 03:25.640 and you can see who has approved that and all those tiny nitty gritty details within your links for 03:25.640 --> 03:26.810 the development or here. 03:26.810 --> 03:31.700 So these are really cool things that we can see within the task and all these integrations that are 03:31.700 --> 03:36.950 happening right now is kind of very very seamless and you can see all these great things happening within 03:37.190 --> 03:38.450 as you know up service. 03:38.540 --> 03:43.790 So now you can see that the your board and as your repos are kind of very tightly integrated whatever 03:43.790 --> 03:48.600 is happening within the core is also something reflected within your boards of all the tasks and the 03:48.610 --> 03:49.560 work items. 03:49.760 --> 03:54.170 And finally the branch policies again branch policies is something which is there for a pretty long 03:54.170 --> 03:58.690 time with a gift and they have introduced that within the Azure dope service as well. 03:58.730 --> 04:05.270 So you can create the branch policies by protecting this brand to have required a minimum number of 04:05.660 --> 04:08.420 reviewers and check for linked work items. 04:08.540 --> 04:14.960 Take for comment as illusions limit the merge types and you can also add different kinds of bold policies 04:14.960 --> 04:20.810 and you can also have different approval from additional services that if you want so you can do all 04:20.810 --> 04:26.900 sort of jars in the branch policy for a particular brand that you are working with for that particular 04:26.900 --> 04:32.410 Sprint or maybe for that particular feature that you are working with within your code. 04:32.550 --> 04:35.820 So let's quickly see everything in action and understand how things work. 04:35.960 --> 04:37.010 Starting our next video.