All right, so moment of truth, we're now going to make another change on our debt branch.
We're going to push it up to get Hub and expect to see all the tests inside of our service being ran
in parallel.
So in this case, I'm going to open up my order service.
I'll open up the index DFS file and at the very top of my staff function, allowed in a console log
of starting.
So that is the change that I want to add in to my pillow request that I still have running.
It's going to save the file closed out.
I'm gonna go backward to my terminal.
I'm going to check out my dead branch because remember, I want to make this change on the death branch.
So get Check-Out, Dev.
I going to add that change.
I'll do it, get status just to make sure I successfully added it.
Yep.
Looks like I got it under.
Commit it and I'll give this one a message or something like add startup message to order service.
And then I will push that to origin.
Deb?
All right.
So he's scheduled to flip back over to that Pullo request we had created and see all these different
workflows running at the same time.
Let's go to my poller request tab.
I'll go to added startup message.
And if I go down to latest commits, I'll see all four workflows running in parallel and just, you
know, I've noticed that the very first time that you run or add in a workflow, sometimes get Hub doesn't
really want to process it right away.
So if you just sit here and wait for a while and don't see any progress being made or if some of the
or one of these is just stuck in a this check has started or something like that state for five minutes
or so, then you can always click on details.
Click on cancel workflow on the right hand side and then make another change to your local repository
on the dev branch.
Push it back up and let these things run again.
Again, you only have to do that if it looks like everything is stalled out for about five minutes or
so.
OK, so it looks like my orders tests have passed successfully and I can easily look around, take a
look at the off tests.
Looks like those are still running.
I can take a look at the payments tests.
It looks like those are running as well, but also looks like some them are starting to be a result.
So I'm going to go backward to my poultry quest itself.
Here's the pull request.
And I'll just wait here.
And after a minute or two, after all the tests run.
Yeah.
Looks like we're good to go.
I've now ran all the different tests across all my different services.
They ran rather quickly because they all ran in parallel.
Now I can safely merge this Polari question because I'm pretty confident that, hey, I've made some
changes and I have not broken anything inside my application.
OK.
So this looks good.
And we've now taken care of this workflow all the way up to the point where.
We have all of our test passing now in theory, if we merge this PRR into the master branch.
We want to somehow take this updated master branch and somehow deploy these changes.
That's be the next big thing.
We start to work on actually deploying our code after merging IPR into the master branch.