1
00:00:00,310 --> 00:00:04,030
In stage one with Alison you
created a new repository.

2
00:00:04,030 --> 00:00:06,670
That repository is owned by your user.

3
00:00:06,670 --> 00:00:09,970
In an organization like Acme Inc
the repository should be

4
00:00:09,970 --> 00:00:11,795
owned by the organization instead.

5
00:00:11,795 --> 00:00:16,320
Let's start by creating a new repository
in the organization, give it a little bit

6
00:00:16,320 --> 00:00:21,110
of content, and give our developers
team access to the new repository.

7
00:00:21,110 --> 00:00:25,830
From the GitHub dashboard click the plus
icon on the top right of the page, and

8
00:00:25,830 --> 00:00:28,500
choose new repository.

9
00:00:28,500 --> 00:00:30,730
This screen should look pretty familiar,
but

10
00:00:30,730 --> 00:00:33,200
we need to do something
a little different.

11
00:00:33,200 --> 00:00:36,960
Where you see your username you'll
wanna choose your organization.

12
00:00:36,960 --> 00:00:40,340
I'm going to choose kdaigle-inc.

13
00:00:40,340 --> 00:00:44,229
Choosing kdaigle inc means the repository
will be owned by the kdaigle inc

14
00:00:44,229 --> 00:00:45,830
organization.

15
00:00:45,830 --> 00:00:50,360
You can name the repository magnum opus.

16
00:00:52,130 --> 00:00:55,520
Okay, let's make this repository public.

17
00:00:55,520 --> 00:00:59,340
Public repositories are free, but
you may want to use private for

18
00:00:59,340 --> 00:01:01,780
any real code within your organization.

19
00:01:01,780 --> 00:01:06,910
Next, click the check box that says
initialize this repository with a readme.

20
00:01:06,910 --> 00:01:10,830
This will give us a simple text
based readme to start working with.

21
00:01:10,830 --> 00:01:13,130
All right, click create repository.

22
00:01:14,550 --> 00:01:15,430
There you go.

23
00:01:15,430 --> 00:01:19,080
You have a brand new repository
owned by your organization.

24
00:01:19,080 --> 00:01:22,710
We have a really simple readme all set and
ready to go.

25
00:01:22,710 --> 00:01:26,410
At the moment only you can
access the repository.

26
00:01:26,410 --> 00:01:30,250
Let's give access to the developers
team we created in the last video.

27
00:01:30,250 --> 00:01:33,980
At the top of your repository
click the settings tab.

28
00:01:33,980 --> 00:01:37,780
This will bring us to settings
specific to our repository.

29
00:01:37,780 --> 00:01:41,150
On the left side bar click
collaborators and teams.

30
00:01:42,220 --> 00:01:45,150
At this point the screen
will be pretty blank.

31
00:01:45,150 --> 00:01:47,150
You just created the repository and

32
00:01:47,150 --> 00:01:50,310
we haven't given anyone else in
the organization access yet.

33
00:01:50,310 --> 00:01:54,570
On this screen you have two options to
give people access to the repository

34
00:01:54,570 --> 00:01:57,520
using teams or using collaborators.

35
00:01:57,520 --> 00:02:01,320
Like in the last video teams are great
when you have a functional area,

36
00:02:01,320 --> 00:02:04,560
skill set, or a project that
you'd like to group people by.

37
00:02:04,560 --> 00:02:09,520
Sometimes though you only wanna grant
a single person access to the repository.

38
00:02:09,520 --> 00:02:13,380
This is useful when you have a rare
exception or you have someone outside your

39
00:02:13,380 --> 00:02:17,600
organization that you'd like to give
access to just this one repository.

40
00:02:17,600 --> 00:02:20,090
This is when you'd use
the collaborators feature.

41
00:02:20,090 --> 00:02:24,290
For our repository since it's a product
our whole team will be working on

42
00:02:24,290 --> 00:02:26,800
we should give access
to the developers team.

43
00:02:26,800 --> 00:02:31,150
Click the add a team button,
and then in the drop down

44
00:02:31,150 --> 00:02:34,870
we'll select the developers team that
we created in the previous video.

45
00:02:36,070 --> 00:02:39,680
Now we'll need to choose the level of
access the developers team should have to

46
00:02:39,680 --> 00:02:41,310
this repository.

47
00:02:41,310 --> 00:02:43,940
There are three permission levels.

48
00:02:43,940 --> 00:02:46,310
Admin, write, and read.

49
00:02:47,600 --> 00:02:50,310
Read means you can only read the code.

50
00:02:50,310 --> 00:02:52,890
Write means that you can write
the code as well as a few

51
00:02:52,890 --> 00:02:57,190
other things in the repository like
creating labels and milestones.

52
00:02:57,190 --> 00:03:00,040
Finally admin means you can read,
write, and

53
00:03:00,040 --> 00:03:03,600
manage the settings in access
like we're doing right now.

54
00:03:03,600 --> 00:03:06,930
For the developers team
write makes the most sense.

55
00:03:06,930 --> 00:03:09,870
We want them to be able to
make changes to the code, but

56
00:03:09,870 --> 00:03:13,660
not allow them to give others
access to the repository.

57
00:03:13,660 --> 00:03:16,190
Let's go ahead and give them write access.

58
00:03:16,190 --> 00:03:16,980
That's it.

59
00:03:16,980 --> 00:03:19,520
Now we have an organization
owned repository and

60
00:03:19,520 --> 00:03:22,480
we've granted the developers team
the ability to make changes to

61
00:03:22,480 --> 00:03:25,690
the code
>> In the next video we'll cover creating

62
00:03:25,690 --> 00:03:28,570
a great poll request for
code review within your organization.