Hi guys My name is Scott.
Take an I am from is it I mentioned dot com and welcome to another section of our continuous integration
development and delivery with Azure doe ops course.
And in this section we are going be talking about as you repost and this video we are going to be talking
about an introduction to Azure repos as your reporter said our version control tool that you can use
to manage your code whether you're a software project is a large or small project using version control.
As soon as possible it's a good idea.
And again as your reports provide support for two types of version control systems in Azure which is
good and TAF we see so they get is something that we know it can be a good enterprise or good that they
are using the organization.
It is exactly the same get flavor which is something that you have pretty much used to.
And again you get to something which recently Microsoft acquired so you can see all the different integration
coming in for the favor of gain.
Is also really really awesome.
Within a year though ups servers and the next page which is supported is t of visa our team foundation
version control.
So if I remember the team foundation version control is very very classical and it's been used across
the companies even Microsoft team are actually using team foundation version control system for their
own internal products and it is something that you can only use for the private project.
So the product that we have created in this course is a public project so we cannot actually use the
TFC.
So if we use that we are going to be encountering some error or something like that.
So rather we are going to be getting into the get off the version control systems for this whole course.
And also when you import the card you can also see that our different kinds of sources it is going to
ask something like as your rep will get or get get enterprise server some version bid bucket or other
get that you are pretty much familiar with.
So you can keep on using any one of the source when importing the core.
You are going to perform at release pipeline and again don't worry about these things yet we are going
to be talking about that in our next section.
But in this section we are gonna be dealing something about as your reports are not so with Azure repos
we can do exact same things that we expect to happen with a get RDF easy on code such as creating a
pull request linking the work item to the pull requests setting up a branch policy squash merge pull
request get branch pull requests workflow leaving commons and vote on changes so leaving Commons and
the vote on changes or something pretty new to the game itself and you can keep on adding some smileys
and all those tough features introduced NTFS which was introduced in the bird conference earlier this
year and this is really awesome to see that all these fancy little things are something which community
was expecting to happen for a pretty long time now.
And linking the comments with the task we can also do that as well as you can see there are some tasks
that we could no previous videos and you can see that we can also add the link for the task.
So for instance if I have a link for the source card for the particular brands that we are working for
the speaker of sprint you can link that and once the code has been completed by the developer and once
he is checking in and once it has been approved you can also see the status of the approved being happened
and you can see who has approved that and all those tiny nitty gritty details within your links for
the development or here.
So these are really cool things that we can see within the task and all these integrations that are
happening right now is kind of very very seamless and you can see all these great things happening within
as you know up service.
So now you can see that the your board and as your repos are kind of very tightly integrated whatever
is happening within the core is also something reflected within your boards of all the tasks and the
work items.
And finally the branch policies again branch policies is something which is there for a pretty long
time with a gift and they have introduced that within the Azure dope service as well.
So you can create the branch policies by protecting this brand to have required a minimum number of
reviewers and check for linked work items.
Take for comment as illusions limit the merge types and you can also add different kinds of bold policies
and you can also have different approval from additional services that if you want so you can do all
sort of jars in the branch policy for a particular brand that you are working with for that particular
Sprint or maybe for that particular feature that you are working with within your code.
So let's quickly see everything in action and understand how things work.
Starting our next video.