WEBVTT

00:04.560 --> 00:09.920
It is important that before we start the CI CD section, that you commit all the changes that we have

00:09.920 --> 00:10.760
done so far.

00:10.920 --> 00:16.400
The best practice which we have mentioned already, but I will repeat again, is that when you do a

00:16.400 --> 00:21.520
change in your code, let's say adding a new function or changing an already present function, you

00:21.520 --> 00:23.040
should commit that change.

00:23.080 --> 00:28.080
In our case, this isn't something we have followed to the letter, but we made sure that we commit

00:28.080 --> 00:30.280
and push at the end of every section.

00:30.480 --> 00:35.720
And don't worry, even if you didn't do this while going through the course, this won't impact what

00:35.720 --> 00:37.600
we will be doing in the section.

00:37.640 --> 00:44.480
What is important at this point is that before we move on, we need to commit and push any changes that

00:44.480 --> 00:45.760
are not being tracked.

00:45.880 --> 00:52.000
In my case, all the changes we did in the last section for the testing I committed and pushed already.

00:52.160 --> 00:54.000
So there are no pending changes.

00:54.400 --> 01:00.120
You would be able to see the changes if, for example, I had to do a change, let's say in my docker

01:00.120 --> 01:07.400
compose, let's do a save and then the source control, you will find that you will have one pending

01:07.400 --> 01:07.920
change.

01:08.120 --> 01:09.680
In my case this isn't the case.

01:13.800 --> 01:19.680
But if in your case you still have some pending changes, I will remind you that there are those three

01:19.680 --> 01:24.160
steps where you need to add any changes.

01:24.200 --> 01:28.840
Once you press enter, then you have to commit those changes with a comment.

01:29.400 --> 01:36.720
Let's say a commit message that you want to do and then simply git push like that.

01:36.760 --> 01:41.840
Our code is being versioned and now we can move on to the GitHub workflow.