1
00:00:01,550 --> 00:00:03,170
All right, so let's test out this workflow.

2
00:00:03,390 --> 00:00:05,660
So we're going to begin on this first step right here.

3
00:00:05,690 --> 00:00:08,690
We're going to make changes to some service inside of our project.

4
00:00:09,290 --> 00:00:11,330
In this case, the changes don't really matter all that much.

5
00:00:11,360 --> 00:00:13,280
I just want to have some change we can commit.

6
00:00:13,960 --> 00:00:17,230
But how about we try out going into our OTT service by me?

7
00:00:17,250 --> 00:00:19,160
The index use violence either.

8
00:00:20,700 --> 00:00:23,600
And how about right at the very start of our start function?

9
00:00:23,940 --> 00:00:26,620
Let's just add in a little console log of starting up.

10
00:00:28,220 --> 00:00:28,580
That's it.

11
00:00:28,610 --> 00:00:30,020
That's the change we want to commit.

12
00:00:31,470 --> 00:00:33,620
So I got to say this file and close it out.

13
00:00:34,820 --> 00:00:35,510
That's step one.

14
00:00:35,930 --> 00:00:40,280
And I can move on to step two, where we are going to commit that code to a new branch.

15
00:00:41,060 --> 00:00:42,110
Back over at my terminal.

16
00:00:43,940 --> 00:00:47,650
I'm going to check out a new branch with Get Checkout's.

17
00:00:48,990 --> 00:00:49,500
Ashby.

18
00:00:50,050 --> 00:00:53,600
And I'll give this branch a very simple name of Deb short for development.

19
00:00:55,370 --> 00:00:58,820
Once I've created that new branch, I'll check my status.

20
00:00:59,180 --> 00:01:00,800
There's the file that we just changed.

21
00:01:01,130 --> 00:01:07,610
We're going to add that and committed with the message of added startup message.

22
00:01:10,650 --> 00:01:13,500
So we just change or committed those changes to a new branch.

23
00:01:13,730 --> 00:01:15,810
It was a branch that was not the master branch.

24
00:01:15,840 --> 00:01:17,100
That's a very critical part here.

25
00:01:17,160 --> 00:01:19,320
We're not going to commit directly to the master branch.

26
00:01:20,310 --> 00:01:25,420
Now we're going to push that branch up to get hub, so to do so, we'll do a get push.

27
00:01:25,600 --> 00:01:26,200
Origin.

28
00:01:31,430 --> 00:01:32,300
Ken looks good.

29
00:01:32,990 --> 00:01:35,420
Looks like we created a new branch.

30
00:01:36,620 --> 00:01:37,160
On GitHub.

31
00:01:38,150 --> 00:01:40,280
So get help as now receive that updated branch.

32
00:01:41,190 --> 00:01:42,990
We're now going to log onto get Hub.

33
00:01:43,200 --> 00:01:47,550
We're going to take a look at a repository and we're going to create a pull request manually to merge

34
00:01:47,550 --> 00:01:49,200
that branch into our master.

35
00:01:49,950 --> 00:01:51,240
So back at my GitHub repo.

36
00:01:52,190 --> 00:01:53,900
I'm going to go to the Apollo request tab.

37
00:01:55,690 --> 00:02:00,340
I can either click on this, compare and pull request button right here for Dev or I can create the

38
00:02:00,340 --> 00:02:01,570
Met police request manually.

39
00:02:02,020 --> 00:02:05,680
I'm going to show how to create it manually because we don't always see this yellow box appear right

40
00:02:05,680 --> 00:02:06,000
here.

41
00:02:06,880 --> 00:02:10,660
So I can either click on the first screen, one in this case and go to new play request.

42
00:02:12,500 --> 00:02:17,090
I'm then going to be prompted with what I am taking code from or which branch I'm going from, which

43
00:02:17,090 --> 00:02:18,350
branch I'm merging it to.

44
00:02:19,220 --> 00:02:23,930
So I want to go from my def branch and merge that into M..

45
00:02:24,770 --> 00:02:26,570
I should see in these dropdown master.

46
00:02:26,750 --> 00:02:27,410
And then def.

47
00:02:29,380 --> 00:02:31,100
Well, then click on Create Polari Quest.

48
00:02:32,840 --> 00:02:36,140
We get prompted to add in a message, so a title for the play request itself.

49
00:02:36,170 --> 00:02:38,780
And then some description right here of the changes that we are making.

50
00:02:39,410 --> 00:02:43,550
So in theory, we would want to put in some description of what just happened to her, why I'm trying

51
00:02:43,550 --> 00:02:44,950
to merge this code into M..

52
00:02:45,710 --> 00:02:50,930
I might put in a description here that says something like it would be nice if we had a.

53
00:02:52,930 --> 00:02:56,020
Message whenever the service started up.

54
00:02:57,760 --> 00:02:59,020
And I'll create the play request.

55
00:03:01,470 --> 00:03:06,630
So once I create that play request, it triggers a new event on GitHub and that event should trigger

56
00:03:06,750 --> 00:03:09,240
the get help action or that workflow we just put together.

57
00:03:09,830 --> 00:03:14,790
So after a moment or two, you should see the box down here start to light up or change as you go over

58
00:03:14,790 --> 00:03:15,210
to yellow.

59
00:03:15,240 --> 00:03:17,790
And I should say something like some checks haven't completed yet.

60
00:03:18,740 --> 00:03:21,110
So that is our GitHub action being executed.

61
00:03:21,530 --> 00:03:25,850
In theory, it's going to run our tests and give us some output on those tests right here inside this

62
00:03:25,850 --> 00:03:28,370
window to get more information about what's going on.

63
00:03:28,400 --> 00:03:29,870
We can click on details on the right.

64
00:03:31,100 --> 00:03:36,700
And it's going to take us to some information about the running job in this case, it has is going through

65
00:03:36,700 --> 00:03:38,080
essentially the script we just put together.

66
00:03:38,110 --> 00:03:43,420
You can see that right now it is running ECD into off and install in NPM run test command.

67
00:03:44,960 --> 00:03:49,890
So after it has installed all those dependencies, it's going to run all of our tests and hopefully

68
00:03:49,890 --> 00:03:53,580
they all pass, if they pass, then this step will be resolved successfully.

69
00:03:53,610 --> 00:03:55,140
Otherwise, if they fail for some reason.

70
00:03:55,410 --> 00:03:59,570
Well, the overall test suite is going to fail and we'll be told about that back inside of our Pullo

71
00:03:59,580 --> 00:04:00,030
request.

72
00:04:00,720 --> 00:04:03,330
So looks like in this case, all my tests ran successfully.

73
00:04:03,600 --> 00:04:08,160
So I get a green checkbox right there, green checkbox right here to say everything looks good.

74
00:04:09,650 --> 00:04:11,940
So if I go back over to the conversation tab.

75
00:04:13,500 --> 00:04:15,360
Which is essentially the main pillar request tab.

76
00:04:15,950 --> 00:04:18,120
I'll now see something it says All checks have passed.

77
00:04:18,540 --> 00:04:23,610
So that'll be assigned to you and I as developers that the changes I just made didn't break anything

78
00:04:23,610 --> 00:04:24,270
inside of our app.

79
00:04:24,660 --> 00:04:31,200
And we should be safe to now merge this poll request into our master branch so I could click on merge

80
00:04:31,350 --> 00:04:32,160
request right there.

81
00:04:32,280 --> 00:04:33,000
But I'm not going to.

82
00:04:33,030 --> 00:04:37,050
Right now, I want to show you what would happen if one of our tests failed for some reason as well.

83
00:04:39,560 --> 00:04:40,400
Let's take a pause right here.

84
00:04:40,440 --> 00:04:40,780
Welcome back.

85
00:04:40,870 --> 00:04:41,300
Nice video.

86
00:04:41,340 --> 00:04:46,470
We're gonna take a look at what happens if one of our tests, failure fail during this pullet request

87
00:04:46,490 --> 00:04:47,150
process.