Added git push to CLI basics.

gitcli-basics/README.md

@@ -92,6 +92,32 @@ The following screenshot shows the result of a commit on our pet project after t
   - The last lines of the commit show a summary of what has been actually committed.
 
 
+## Propagating local changes to the remote repository
+
+To update a remote repository with all the commits that have been made locally, the `git push` [[command](https://git-scm.com/docs/git-restore)] is used. It needs no arguments or options, because it "knows" which part of the history is local and needs to be propagated to the remote repository.
+
+To know what will be propagated, you can use `git status` as in the following example:
+
+![status_before_push.png](./media/status_before_push.png)
+
+It shows that the local repository is one commit *ahead* of the remote repository. Meaning, that one local commit (the latest) will be propagated to the remote repository.
+
+The actual output of `git push` looks like:
+
+![git_push.png](./media/git_push.png)
+
+Notice the last line, with two commit ids (the one of the latest commit when cloning the repository, and the latest local commit id), and the names of the branches involved in the commit.
+
+On GitLab, the project welcome page displays information about the latest commit that has been pushed to the repository.
+
+![gitlab_after_push.png](./media/gitlab_after_push.png)
+
+
+
+
+
+
+