In the last video, we created our first GitHub hook.
We're not going to try to test this thing out.
So our ultimate goal is to be able to create a pull request and see all the tests for specifically our
art service get executed.
Now, one thing on to point out is that inside this little script we put in NPM run test Kolan S.I.
So why is that?
Well, whenever we run our tests inside of this GitHub environment, we need to make sure that our test
suite exits automatically at some point time.
Right now, our NPM run test command is going to start up just inside the wotcher mode.
So it's going to run continuously.
Just watching for changes to be made to our source code.
We do not want that when we're running our tests on GitHub.
We want just one run of our test suite and we want to exit entirely rather than running NPM test directory
directly.
We're going to instead create a new script called Test in S.I that is going to run our test suite exactly
one time and then automatically exit.
So let's go back over to our OTT service and make that change very quickly.
Inside my service, I'll find the package not just on file.
I'll find the script section inside there and I'm going to add in a new script of Test Colin S.I.
And the command for that, we're going to put in just.
And we actually don't even need that no cash command on there at all.
We definitely do not want.
Watch all as you imagine.
That's what starts up our test suite in the watcher mode.
Well, then save this.
We're going to go over to our terminal.
We're going to commit these changes on the master branch because this is some initial configuration
we're going through.
We're gonna push this up to get hub.
And then after that, we'll make some other small change for our project to kind of simulate making
a change.
This thing in the real world and then push it up to get up and walk through our entire workflow.
So back over at my terminal.
I'll do it.
Get status.
Take a look at the files I've changed.
Just that package stays on file.
It's all adults and uncommitted.
With the message.
And then finally, I'm going to push this up once again to the master branch.
Get push origin master.
And all right, my mistake, we just made a change on GitHub to the master branch.
We have to pull those changes down first.
We need to do a get whole origin, master.
That's better.
You're probably gonna see a little editor pop up asking you to provide a merge message to go through
that process, and once we merge everything, then we can do a get push.
Origin Master.
All right, so there's our changes.
Now, in theory, ah, get hub workflow is all ready to be tested.
Let's pause once more.
Come back.
Next video.
Try making a change and simulate the real workflow that we're going to go through.