It is important that before we start the CI CD section, that you commit all the changes that we have
done so far.
The best practice which we have mentioned already, but I will repeat again, is that when you do a
change in your code, let's say adding a new function or changing an already present function, you
should commit that change.
In our case, this isn't something we have followed to the letter, but we made sure that we commit
and push at the end of every section.
And don't worry, even if you didn't do this while going through the course, this won't impact what
we will be doing in the section.
What is important at this point is that before we move on, we need to commit and push any changes that
are not being tracked.
In my case, all the changes we did in the last section for the testing I committed and pushed already.
So there are no pending changes.
You would be able to see the changes if, for example, I had to do a change, let's say in my docker
compose, let's do a save and then the source control, you will find that you will have one pending
change.
In my case this isn't the case.
But if in your case you still have some pending changes, I will remind you that there are those three
steps where you need to add any changes.
Once you press enter, then you have to commit those changes with a comment.
Let's say a commit message that you want to do and then simply git push like that.
Our code is being versioned and now we can move on to the GitHub workflow.