1
00:00:00,270 --> 00:00:01,460
Welcome back, everyone.

2
00:00:01,470 --> 00:00:08,340
So this section is all about collaboration, workflows, different ways of configuring a repository

3
00:00:08,340 --> 00:00:16,079
and different ways of working on branches when to create branches, how to merge changes, how to ask

4
00:00:16,079 --> 00:00:18,270
to merge changes, how to get permission.

5
00:00:18,270 --> 00:00:24,300
We won't be seeing any new git features or new git commands rather, but we will be spending kind of

6
00:00:24,300 --> 00:00:26,970
a lot of time talking about workflows.

7
00:00:27,270 --> 00:00:32,759
I considered breaking this up actually because it is a long section and I recommend that you take your

8
00:00:32,759 --> 00:00:40,890
time and probably I would split up viewing this section, maybe even go on to some of the later concepts

9
00:00:40,890 --> 00:00:47,490
like rebasing or git tags if you want to break something that's a bit a bit breezier and then come back

10
00:00:47,490 --> 00:00:53,450
to finish up this section because it's all pretty important stuff, but it's also just a lot.

11
00:00:54,090 --> 00:01:00,000
So we're going to start by talking about the problems with working in what I call a centralized workflow.

12
00:01:00,000 --> 00:01:01,260
Working on one branch.

13
00:01:01,380 --> 00:01:07,290
It's important to understand then we cover the feature branch workflow critical.

14
00:01:07,290 --> 00:01:09,840
We talk about something called pull requests.

15
00:01:09,840 --> 00:01:10,920
Very important.

16
00:01:10,920 --> 00:01:16,290
If you plan on working with collaborators, if you plan on working on open source projects, if you

17
00:01:16,290 --> 00:01:22,530
want to use gits in some sort of work environment where there are other people pass or pull requests

18
00:01:22,530 --> 00:01:24,360
are used all the time.

19
00:01:24,360 --> 00:01:27,270
I put branch protection rules in important.

20
00:01:27,270 --> 00:01:33,390
This is a thing we can change a setting on GitHub it's important to know about, but just not as critical

21
00:01:33,390 --> 00:01:34,530
as these other things.

22
00:01:34,530 --> 00:01:40,320
I'm going to show you something on GitHub called Forking and then we spend a decent chunk at the end

23
00:01:40,320 --> 00:01:47,250
of the section three, three or four videos talking about forking and a workflow called Fork and Clone.

24
00:01:47,250 --> 00:01:48,690
That's what I call it at least.

25
00:01:49,200 --> 00:01:56,160
And this is heavily used for open source projects, big projects like React or VS Code, which is open

26
00:01:56,160 --> 00:01:58,710
source TensorFlow.

27
00:01:58,710 --> 00:02:03,510
Just any big open source project you can think of that have thousands of collaborators.

28
00:02:03,510 --> 00:02:07,500
They don't grant every collaborator full permissions just to push up.

29
00:02:07,500 --> 00:02:12,660
So the fork in clone workflow is employed in those scenarios, and it's worth knowing about if you plan

30
00:02:12,660 --> 00:02:16,050
on making open source contributions, which is always a good idea.

31
00:02:16,080 --> 00:02:21,030
Anyway, there's a lot of stuff in this section, all workflow oriented, lots of diagrams.

32
00:02:21,030 --> 00:02:26,790
I'm pretty proud of some of the diagrams you got to say take forever to make them, but I think hopefully

33
00:02:26,790 --> 00:02:28,110
some of them are useful.

34
00:02:28,140 --> 00:02:29,550
Let's go ahead and get started.

35
00:02:29,550 --> 00:02:30,660
You'll be the judge of that.

36
00:02:30,660 --> 00:02:31,650
Okay, bye.