removed external image links

README.md

@@ -28,8 +28,7 @@ For a detailed explanation of how git works, and how it can be useful for other
 #### Git Workflow
 As you get used to working in git, it may be helpful to visualize what you are doing as a repeatable sequence of steps. In addition to the guides above, you may find the graphic below helpful for your reference:
 
-
-<img src="https://elevationusvistttest.s3.us-west-1.amazonaws.com/gitcheatsheet.png" alt="git workflow" width=50%/>
+<img src="./git/images/gitcheatsheet.png?raw=true" alt="git workflow" width=50%/>
 
 ## Learn These Python Packages
 

git/git-1_why_we_use_git_and_gitlab.rst

@@ -38,7 +38,7 @@ Diffs
 Git also automatically produces an output called a diff that shows the line-by-line edits made in each commit. Diffs pinpoint the exact differences between file versions and provide a powerful way to understand version details and commit messages left by users. Below is an example of a diff showing changes someone made to a text file called index.md. This diff shows us the updating_the_geo_nodes.md line was deleted and the version_specific_updates.md line was added . Notice how
 this diff identifies only the exact part of the line that changed, as the “ing” stays the same between commits!
 
-.. figure:: https://elevationusvistttest.s3-us-west-1.amazonaws.com/git/text-commit-ss.png
+.. figure:: ./images/text-commit.png?raw=true
    :alt: GitLab diff :scale: 50 %
 
 Diffs are only visible with git for certain filetypes. Git was origially designed to deal with code for software development, so filetypes associated with most programming languages work great in git. For example, git will track commits and diffs for files like…
@@ -67,7 +67,7 @@ If we make a commit with these files, we won’t be able to see the diff! Below
 commit history. However, the diff cannot show what changed. The user is stuck with figuring out the differences between the original file and
 this new version. The only information provided is the commit message, “Added point and changed date”. For large files, this limited information may not be useful enough to track changes. It is often difficult to manage large, distributed projects without seeing the diffs.
 
-.. figure:: https://elevationusvistttest.s3-us-west-1.amazonaws.com/git/shp-commit-ss.png
+.. figure:: ./images/shp-commit.png?raw=true
    :alt: GitLab diff shp :scale: 50 %
 
 What text-based filetypes should we use?

git/git-2_clone.rst

@@ -57,7 +57,7 @@ clone, and copying what shows up under "https". Once cloned, you will have
 the contents of that repository inside a new folder within your chosen
 file directory. Note: This new folder will be your git repository.
 
-.. figure:: https://docs.gitlab.com/ee/user/admin_area/settings/img/clone_panel_v12_4.png
+.. figure:: ./images/clone_panel.png?raw=true
    :alt: Clone Repo GitLab
 
 

git/git-3_branch-commit-push.rst

@@ -21,7 +21,7 @@ Now, if you type ``git status`` you should see, once again, that you are “On b
 
 |image0|
 
-.. |image0| image:: https://git-scm.com/book/en/v2/images/head-to-testing.png
+.. |image0| image:: ./images/branches.png?raw=true
 
 Borrowing from git’s documentation, “A branch in Git is simply a lightweight movable pointer to one of these commits. The default branch name in Git is master. As you start making commits, you’re given a master branch that points to the last commit you made.” But you can create as many branches as you want. You can read more about branches `here <https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell>`__.
 
@@ -119,4 +119,4 @@ That’s it!
 
 You should now see the updated end_of_tutorial.txt file with your name on GitLab on the develop branch!
 
-The process we just followed is visualized in this `cheat sheet <https://elevationusvistttest.s3-us-west-1.amazonaws.com/gitcheatsheet.png>`__. You can follow this each time you work on a file.
\ No newline at end of file
+The process we just followed is visualized in this `cheat sheet <./images/gitcheatsheet.png?raw=true>`__. You can follow this each time you work on a file.
\ No newline at end of file