Welcome back, everyone.
So this section is all about collaboration, workflows, different ways of configuring a repository
and different ways of working on branches when to create branches, how to merge changes, how to ask
to merge changes, how to get permission.
We won't be seeing any new git features or new git commands rather, but we will be spending kind of
a lot of time talking about workflows.
I considered breaking this up actually because it is a long section and I recommend that you take your
time and probably I would split up viewing this section, maybe even go on to some of the later concepts
like rebasing or git tags if you want to break something that's a bit a bit breezier and then come back
to finish up this section because it's all pretty important stuff, but it's also just a lot.
So we're going to start by talking about the problems with working in what I call a centralized workflow.
Working on one branch.
It's important to understand then we cover the feature branch workflow critical.
We talk about something called pull requests.
Very important.
If you plan on working with collaborators, if you plan on working on open source projects, if you
want to use gits in some sort of work environment where there are other people pass or pull requests
are used all the time.
I put branch protection rules in important.
This is a thing we can change a setting on GitHub it's important to know about, but just not as critical
as these other things.
I'm going to show you something on GitHub called Forking and then we spend a decent chunk at the end
of the section three, three or four videos talking about forking and a workflow called Fork and Clone.
That's what I call it at least.
And this is heavily used for open source projects, big projects like React or VS Code, which is open
source TensorFlow.
Just any big open source project you can think of that have thousands of collaborators.
They don't grant every collaborator full permissions just to push up.
So the fork in clone workflow is employed in those scenarios, and it's worth knowing about if you plan
on making open source contributions, which is always a good idea.
Anyway, there's a lot of stuff in this section, all workflow oriented, lots of diagrams.
I'm pretty proud of some of the diagrams you got to say take forever to make them, but I think hopefully
some of them are useful.
Let's go ahead and get started.
You'll be the judge of that.
Okay, bye.